Update to Security Update 2017-002 16G1114

Hi all,

I'm 99% sure this is a stupid mistake caused by my own ignorance. Would appreciate some direction though :)

I've got a Gigabyte GA-Z270M-D3H, i7-770K, EVGA GTX 1060 6Gb SSC with a Samsung 960 NVMe drive on my Sierra hackintosh.

I was trying to figure out the best way to apply the 2017-0002 update. From what I understood going in, it probably made sense to update the Clover bootloader, but other than that I'd be good to go. For fear of screwing up, I cloned the NVMe drive onto a 4Tb SATA disk (minus the users directory as that's already backed up elsewhere). So, worst case scenario I can start from scratch and copy my files over, no biggie. But, I'd rather learn how to fix my screw ups than remain a n00b forever.

Anyway, prior to the update I had ran the RehabMan patch nvme script with the spoof option (not sure if I needed to do this - not dual booting on the same drive?). From what I understand I probably should have done this after applying the security update, but it was all working good before the updates even after reboots, so I figure there was no harm done. I continued with the update and Clover detects the NVMe drive okay, but constantly boots into a kernel panic: https://imgur.com/a/HNWb0

(Not sure if any of the things I covered up were serial numbers/unique to me ..can't beat a bit of healthy paranoia! 😂)

So, stupid question - given Clover can see the NVMe drive, is it fair to assume that it's nothing to do with the NVMe kext?

I'm half tempted to upgrade to 10.13 High Sierra given NVMe is natively supported, so would be one less thing to worry about. But, generally I prefer to steer clear of Apples latest until it hits 10.x.5 or something.

Any help is appreciated, thanks!

tl;dr - Tried to apply 10.12.6 2017-0002 security update, Clover can see/attempts to boot ..does that mean my NVMe kext is still good and the issue is more likely to be something else?