There are JB apps similar to those. I'll admit they are not as robust in the settings, mainly cause devs know there's not a huge demand for battery saving on the iPhone vs the demand for it on Android. But if Devs want to make the same exact apps for the iPhone, they could easily do so and distribute it via Cydia or whatever.
I looked, there is NOTHING on iOS that is even close to what Tasker can do. You asked to see what Android can do that jailbroken iOS can't, so I showed you some. Now you're saying "well ok, iOS can't do that, but someone can make an app that can!" Stop changing the argument, there's a difference between an actual product (Tasker) and vapourware (your iOS promises)
SBSettings does the job for me.
SBSettings and titanium back have completely different functions
Well iOS5 won't require iTunes. I myself have never minded backing up via iTunes. Unless I was to backup 100 times a week, I really don't care much about OTA much for entire backups.
Here you go again changing the target of the argument, once again, you asked what Android can do that jailbroken iOS can't in general, now you're saying that "well it's not important to me so its not a valid argument". Also are we debating what Android can do now vs what iOS can do in the Fall? If so, then your OS5 argument doesn't apply, otherwise I can say that Ice Cream Sandwich will be able to do everything iOS can and more!
This is device specific and not all Android devices have SD slots. And OTA will be here iOS5.
Also iOS & Android are to differ beasts.
IMO, iOS out of the box is already optimized to work extremely smooth ... so all that's really needed is a jailbreak for added functionality. There's really no reason for custom ROMs on the iPhone.
Android on the other hand is a whole differ story. It's more like the WM6 & below days. Devs will cook up a ROM that's better optimized to work for a specific device(s) mainly to solve a problem or cause the default ROM is crap. With WM, most ROMs were made for better memory management. With Android the big thing is power management.
Over/Under clocking should not be necessary on any new device. Also (correct me if I'm wrong), but it seems problems that some users are having with animations don't have anything to do with processing power at all. If that were the case, it would be widespread.
your counter-arguments all revolve around "its not important for me, so its moot"
i'm not even going to bother.