The article seems to assume that the user is allowing the task killer to kill apps and run in the background or the user is killing tasks constantly.
I don't do either. If I open up a bunch of apps at once (which I do on occasion) I'd rather kill them all than wait for Android to do it for me. Like I said I'm not letting ATK run in the background and I've set it to ignore all essential processes. I probably use the app once every few days or so when I've just been indecisive about what I want to do on it (and thus opened up about 20 apps).
I regularly get 36-48 hours out of my stock battery, which seems to be above the norm for some folks, so I must be doing something right.
Assuming you have it just kill things you start (NOTHING that starts in the background. That will be VERY counterproductive, costing speed/battery), you're avoid MOST of the risks involved. And you might get some (not a lot, but some) battery/speed advantage. It takes some time (a few minutes) for android to shove the processes into the background, so you might lose a little battery in that time.
Here is why it still might hurt...
1. You kill something that you restart later. Instead of being loaded in the ram already, it has to use CPU/battery to reload the app. This also slows down the phone.
2. Let's say that one of the apps started a system service that uses cpu, network, or keeps the phone from sleeping. When the app is done with that service, it will close out that service. However, if you kill that app after it loads the service but before it ends, you can orphan the service, so it will run continuously. This can drain your battery like a sieve.
3. There is some potential to damage/corrupt files used by running apps. Not really a huge risk, but it's there.
Really I'd say what you're doing is GENERALLY harmless, but isn't really doing you any real good. So on a risk reward basis, you'll probably be better off not using Task Killer (or using the TK built into system panel, and only kill stuff thats using proc).