The issue wasn't cooling; it was how the CPU incorrectly throttle itself that caused it to overheat again too fast.
There's another thermal control unit involved and what people found was that the firmware for it was causing the CPU to drop down to 800mhz instantly when it detected the specific terminal event and when it reset that, it went back up into high-overheating load (such as the benchmark sustaining the high load) instead of staying at the right balance. In other words, it went into a loop of super low power load and then super-high load instead of the middle where the terminal balance is right for the load it is doing. Because of this low/high loop, the performance was not consistent and degraded as the overheating cause it to drop to 800mhz all the time.
Where Apple likely messed up is that the firmware was not placing the CPU at the middle to avoid going into a loop, this allows the CPU to sustain a better CPU performance consistently and for an extended period of time.
There's another thermal control unit involved and what people found was that the firmware for it was causing the CPU to drop down to 800mhz instantly when it detected the specific terminal event and when it reset that, it went back up into high-overheating load (such as the benchmark sustaining the high load) instead of staying at the right balance. In other words, it went into a loop of super low power load and then super-high load instead of the middle where the terminal balance is right for the load it is doing. Because of this low/high loop, the performance was not consistent and degraded as the overheating cause it to drop to 800mhz all the time.
Where Apple likely messed up is that the firmware was not placing the CPU at the middle to avoid going into a loop, this allows the CPU to sustain a better CPU performance consistently and for an extended period of time.