I'm only going to continue replying to educate, because what you're talking about has nothing to do with routines that can damage systems or causing abnormal heat.
Anyone who had overheating and crashing issues with SC2 at the time would have had the exact same issues running a stress test (which most people never run). The problem in that case is that the game was rendering frames as fast as it possibly could, which results in 100% usage regardless of what is going on in the game. It was not going above 100%, and it was not being heated more than any other application running at 100% usage.
Most games do not run at 100% GPU or CPU at all times, unless you have a significant bottleneck or the game is demanding for your machine. This is why people would report a problem with SC2, because they had never experienced it elsewhere (since even Crysis for example may not run the GPU at 100%).
It has nothing to do with routines or 'where' things are coded, it was simply running at 100% and people with poor cooling solutions were getting crashes.
I should also mention that you can't damage a GPU or CPU unless you overvolt it, and even then it's very difficult. Hardware these days all have thermal limits and will shut down (as you know!) if they reach that point, which is well before any damage will be caused.
tl;dr 100% is 100%. If your cooling is bad, your system can throttle or shut down. If your system can't run 100% CPU and GPU without crashing, you have a problem with your hardware.
