Still no solution but I can give some additional info. Even my MBP with Intel Iris Pro when using an external monitor sometimes doesn't wake up the exact same way as my hack. Also a while back Windows users had the same problem until Intel fixed the drivers. Linux had the same problem too some developers got together and fixed the problem. All I can think is that these fixes have not made it to Apple's drivers yet, or they made a partial fix just enough to make MBPs a bit more reliable but the fix has no effect on hackintosh.
Last time I looked into it, I discovered it's caused by a bug in the dynamic display frequency calculation. The first time an external display is initialised it correctly calculates its frequency, however when a display is hot-plugged it fails to calculate and crashes, which you can recreate by unplugging and plugging in your monitor. This kind of bug usually comes about when the developer has not reused the same code for initialisation as for change of state, and it's likely only the init code was tested. On the Mac you'll see "invalid display frequency" output to the console or something similar. The reason why it doesn't happen on MBP internal displays is I believe the frequency settings are known and don't need to be calculated. On Linux they fixed the display frequency calculation and all is good for them now. I don't have it handy but I began to reverse engineer the method in AppleIntelSKLGraphicsFramebuffer.kext in attempt to find the bug, it was tricky though because it was quite different from the Linux driver code I was using as reference.