Years ago, I met the guy who ran the company who made most of the wheels for Rollerblade. He's not a chemist, or an engineer. He's a former helicopter pilot who flew soldiers in and out of the jungles of Vietnam and later became a contract helicopter bush pilot, doing firespotting and transport for the US Forest Service. When he realized he was getting sick of risking his life for not much pay and very little thanks, he started looking for something else to do. Through a friend, he heard that IBM was looking for someone to assist them with an issue with rubber compounds-- they needed a specific rubber formulation for parts that wouldn't degrade even under the worst conditions. He didn't know a thing about rubber, but figured it couldn't hurt to give it a crack. Six months of studying, phone calls, etc, he got a line on it and contacted a friend who worked at a rubber company to produce a prototype. They did, and he presented it to IBM and won a contract, which grew into a business, etc.
The point I'm making is that an open mind is substanitally more important than the chunks of knowledge that you're going to get from a degree. The best programmers I've met had college degrees or no college degrees. One had a master's in Speech Pathology (he ended up designing and implementing lease accounting systems). Another flunked out of college and traded his drum kit for a computer so he could play games (and ended up learning the system from the ground up). Another was driving a forklift in a warehouse and realized the picker routes the ordering system was generating were wrong or hugely inefficent (and ended up redesigning and eventually rewriting the picker system). In each case, they learned the skills they needed along the way.
Having said that, the kind of maths you're looking at are good to have "in the toolkit", not so much for a specific skill, but because they give you a different way of looking at data, problems, solutions, testing, and implementation.
