Whatever the exact number, it doesn't invalidate the point I was making: Switching to ARM will ruin performance for x86 programs, which need to be emulated. ARM has to be significantly faster than x86, or else the emulation overhead will make users hate the transition.
This is a huge challenge for the Mac Pro and rMBP, which are all about performance. Generally, a given microarchitecture can only scale TDP by a factor of 10 by changing frequency and number of cores. Satisfying the pro line would require a new microarchitecture. Considering an x86 to ARM transition would take 1-2 years, that's asking a lot of Apple's chip designers. If Apple was going to go through all the trouble of building a new ARM core for high-performance, high-TDP applications, they might as well build their own x86 CPU. It would save a transition and the necessary emulation overhead. They could roll it out for the MacBook Airs first, then address the Pro line at their leisure (or not and just use Intel CPUs).
That would still be noticeably slower for native software, and unbearable for anything run under emulation. It would also be very painful for use cases such as people wanting occasional Windows applications or Linux VMs.
I do agree that the ~10W you'd save by using an A7 versus an 4250U in a Mackbook Air would be a false economy.
EDIT: To explain that bit about targeted power ranges a bit more, to hit high frequencies at a given process node (like 45 nm or whatever) you need to break up your logic into a fairly high number of simple stages separated by clock driven latches. A core that doesn't worry about hitting high frequencies can divide up it's logic into fewer stages, simplifying design and requiring fewer transistors for latching.
[1]http://www.computingcompendium.com/p/arm-vs-intel-benchmarks...