Sorry for taking so long to reply. I'm crazy busy these days.
Honestly, I uh didn't even know about the HFS+ to APFS without asking policy of the 10.13 installer, and didn't even notice/realize that anything had changed for a embarrassingly long time afterwards. If I had the option, I would have probably opted out, but I also don't care enough to actually go through the trouble of formatting my drive and reinstalling to get back to HFS+.
It also helps that my boot drive is an SSD, which theoretically APFS will someday be the best choice for. But, from a compatibility standpoint, let's just say that it doesn't matter at all. I used my desktop for months without even realizing the boot volume was APFS and not HFS+. I honestly don't think there is anything risky, it's just a file system. The disk is still a GPT disk, your bios can still see it, your bootloader (clover) can find the correct boot partitions and it all just seems to work. I would argue that all the reasons to use or not use APFS are completely 'real mac vs hackintosh' agnostic.
Actually, that's not quite true. If you need to manually fix something in the actual root partition, and you are dual-booting windows, then your options for working with APFS volumes are pretty limited and will require buying some software most likely. This will certainly change over time, but 3rd party support for APFS is limited right now.
That said, you should not be doing anything to your actual APFS partition anyway, as anything you might need to do you can do on the EFI (clover) partition, which remains good ol' FAT32.
I assume when you try to sleep, your machine immediately wakes up? This is the same USB sleep problem seen in less exotic hardware, rehabman has some great tutorials on fixing this.
There is one caveat though, which is you will lose any ability to wake the computer via USB. So no key presses or mouse movements will wake your computer up. You pretty much have to press the power button to wake the computer back up.
I spent a very long time trying to find a solution to this, as this is kind of inconvenient and for me, the entire point of sleep is that one can easily wake the computer out of it simply by attempting to use the keyboard or mouse.
I ultimately traced the issue back to Apple's USB driver kext itself, and the fact that it was interfacing with a slightly different intel chip set, and when the system was put to sleep, the kext was actually disconnecting the virtual hubs of the USB controllers completely, so it was as if one had just unplugged everything from all the USB ports. The specific USB kext was, sadly, one of the parts of Darwin that Apple hadn't really open sourced at all, so the source code was unavailable.
Long story short, Apple's USB driver kext mismanages certain chipset's USB controllers in regards to sleep, so we can work around this using rehabman's DSDT/SSDT USB sleep fix, but there is really nothing to be done (except maybe a binary patch but I was never able to find exactly the bit of code responsible in Hopper) if you want sleep AND usb wake-ability. C'est la vie.