Interesting thanks. I expect though that the MacBook Pro is well able to handle heavy loads. Yes this test was synthetic, but it's a 'Pro' machine. Is consensus here that you shouldn't run it hard because its 'thin and light'?
MacBook Pro is perfectly able to handle heavy loads. And you can use it in any way that suits your needs. Of course, if most of your usage is running sustained heavy loads, then I'd ask myself whether a laptop was a good choice to begin with.
Again, don't get confused because of the high temps. 100 degrees is a (maximal) safe operating temperature according to the CPU's manufacturer. If you want more details: these CPUs are assured by the manufacturer to draw 45 Watts under sustained load while running at least at their base frequency. So these are the numbers around which Apple has designed their cooling and power system. It's easy enough to confirm using Intel Power Gadget that the CPU will max out around using 45-50Watt in sustained operation — and it will also reach its maximal allowed operating temperature at the same time. All in all, it's a careful balancing act — designing the smallest possible cooling system that will allow the CPU to operate exactly within its declared spec.
And sure, a more powerful cooling system + removing the 45Watt restriction would allow the CPU to use more power in sustained operation and thus have better performance. Thats how desktop computers operate, and there are also some large gaming laptops capable of this. Apple prioritises the compact form factor while delivering very high performance. This, again, is all about balancing and tradeoff. For instance, MSI GT75 Titan delivers 20%-30% better CPU performance in Cinebench (using the i9 CPU) than the MacBook Pro, but the MSI is also 2.5 times heavier (at 4.6 kg) and over 6 times larger (looking at total volume). In fact, its power brick alone weights almost as much as the 15" MBP! So there are diminishing returns
You mean sustained workload such as rendering, but that's no guarantee either. Rendering engine, API efficiency, ambient temperatures and workload content are factors too.
No, I mean any CPU-intensive workloads. Which is formally defined as running multiple threads that execute non-NOP instructions (that ideally load most of the CPU ports) across all the existing cores, without sleeping. Rendering could qualify as such operation — assuming, as you said, the rendering engine is able to maintain high CPU utilisation. But it could be just as trivial stuff as adding 1 and 1 and discarding the result. Ambient temperatures are of almost no consequence. If you have threads that continuously dispatch work, the system will try to boost the CPU as hard as it can, which will ultimately end up in it heating its thermal ceiling on a system like MBP which has one (it would be different on a system that is designed to cool more then the CPU can ever output — in that case the CPU will run cooler, but also such cooling system would be rather inefficient).