You're just pulling reasons out of thin air. Any proof project butter causes excessive battery drain? Or how not being 'pure push' is in fact the cause?
Your Nexus 4 is more than likely suffering from this
http://code.google.com/p/android/issues/detail?id=41855
Project butter ramps CPU to 1ghz upon ANY touch event. Two cores chugging at 1ghz each. Why? To combat lag. Effectively, Google just made the CPU more responsive. It's like if you just used the performance governor to begin with.
Ok, then there's the fact that butter makes sure the UI is a dedicated thread that stays running at full speed.
How is this not using more power? The CPU is more responsive, blah blah. Yeah there's things like vsync, but the fundamental issue here is the lack of GPU rendering requiring loads of CPU power being thrown at it. Project butter makes sure the CPU is tasked consistently to maintain 60 fps and also it makes sure the CPU is more responsive so that there aren't slowdowns.
Look, I appreciate lag-free, but this isn't a complete solution. It may be a limitation of Android due to the vast amounts of hardware platforms out there, or whatever excuse there is, but it's not as efficient as say iOS or Windows Phone.
Then there's apps. Lots of apps sync. All apps other than the official Twitter app will pull data on a regular basis. The Facebook app pulls data. In fact Twitter refuses to give you push notifications unless you sync data at an interval. Combine that with your weather widgets, google reader, etc. all pulling data at fixed intervals, it's pretty clear data is used a lot.
In general, I find that it's pretty easy for an Android phone to gobble up data. On an iPhone unless you're actively using apps, data use is far more limited in idle conditions. It's for this reason I could get away with the 200mb plan and see friends getting away on 200mb on an iPhone. On Android? I've never been below 800mb for months, and I'd have to try hard to stay low.
I dual carry an iPhone and Nexus 4. It's a pretty noticeable difference. I've carried many other Android phones also like the SGS2, Nexus S, Nexus One, Motorola Droid. None have had spectacular battery.
As for the wakelock stuff, I've tried custom kernels that got rid of wakelocks. It's not that much better.
Go read the iPhone review where they plot power usage in idle and while the phone is active against other phones out there. The iPhone's idle power consumption is ridiculously low. Like half of the competition.
I'm not saying that this means Android is bad or whatever. Google's going for a different beast. You have all your information at your hands any time. Weather widgets constantly refreshing, facebook timelines updating on widgets, news flashing across your homepage, reading forums on a widget, Google Now prompting you left and right based on your location. Yeah. These things are great. I love it, but it's not like they don't use battery. They dramatically change battery use, so unless you keep your Android phone plain as hell with no apps, there's no way you can idle better than an iPhone.