That's to be expected, of course. Linux maintainers care about the fact that it can run on just about anything. macOS maintainers only care about whether it runs on Macs.

You admit you're using a hackintosh, and then blame Apple when stuff doesn't work?

That's one heck of a mental disconnect.

I didn’t say I blame Apple. It’s not Apple’s responsibility to write drivers for machines they don’t claim to support.

I’m more saying that—although Linux’s support for things like sleep/wake on random machines might be sometimes wonky, the best efforts of the Hackintosh community don’t get macOS to support those same machines any better. It’s the machines that are wonky. (Usually by having horrible off-spec ACPI tables that get patched over with drivers the manufacturer releases only for Windows.)

Which is further to say: it’s not really a failing of macOS or Linux if your hardware won’t sleep/wake correctly, or won’t connect/disconnect from external displays correctly. In either case, it’s because your machine is nonconformant to the specs the drivers were written to follow. The only way to succeed in such an environment is to spend man-decades (Linux) or at least man-years (Hackintosh) reverse-engineering the brokenness and writing heuristics into your drivers that patch over it—or by being such a monopoly player that the OEM does that for you (Windows.)

Breaking news: An OS with a limited set of drivers for the hardware it's specifically designed to be used on, doesn't work very well on hardware it was never intended to be used on. Full story at 11.

OP is nodding to infamous problems with actual macs freezing and rebooting when waking if external displays are connected, which is a pretty common occurrence on high sierra devices.