This is more or less their philosophy. Look at their attempts to squash scripting languages, runtimes & browsers on iOS. There is absolutely zero technical reason for this, it's all to force developers to code to Apple's APIs.
I really doubt you are correct in this. Though the hardware resources available to iDevices are orders of magnitude greater than, say, the original Mac, it's still very easy to bring the CPU to its knees with an ill-chosen line or two of code, and the introduction of even limited multitasking just makes it easier.
I'm not saying there are "absolutely zero" politico-corporate reasons for Apple's decisions in this area, and I can empathize about disliking the tradeoffs in autonomy for iOS developers (the Mac is much less restrictive, and free once you have the hardware), but Apple's had to do a lot of software optimization to assure a reasonable user experience (responsiveness, battery life, etc), and "bare-metal" runtimes that don't work through the public APIs aren't likely to benefit.
You may well be right about Android. Otoh Apple will probably be happy just to skim most of the profits from the smartphone/tablet market as they do now. Both approaches are useful, pick the one that meets your needs.