Hi all, been following for a bit and decided to add my own experience. Sorry for the long post, I hope it doesn't break any rules.
I have a 4k touchscreen version of the 9560, with a Samsung drive and have a successful installation. The only thing that does not work (that I have noticed) is headphone audio which is there but is very very soft (have to put to max to hear anything). Also, I haven't really checked out sleep (will do this in the coming days).
In order to get to this stage I used the 4k folder in the main post and had no issues at first but then had to add IntelGraphicsFixup.kext (in addition to Lilu.kext and WhateverGreen.kext) to /L/E get past a gIOScreenLockState 3 error during startup, after installing clover to the main boot drive. Note that I did not need this for the installation and only appears after adding all other kexts for some reason. When OSX is loading, the screen flashes a couple of times and the logo resizes, but this is not a big deal.
At one point I managed to get VoodooI2C working, but I have since reinstalled because I am no longer dual booting windows. What I remember is that it required some debugging of the default DSDT/SSDTs (a few errors on compile), using their windows 10 patch, finding the deviceid etc.. It worked really well when it worked, almost felt like a real mac touchpad apart from it being a bit jittery sometimes. I might give this another go soon..
For audio, I currently have CodecCommander.kext with SSDT-ALC298a (I grabbed these two from post #79). AppleALC.kext also, which is not in the "other kexts" within the 4k folder from the main post (not sure about the other one). This didn't solve my problem, and I'm not sure where to go next with this. Attached are my problem reporting zip and clover folders.
P.S.
I also stumbled on something cool while I was dual booting windows: in the BIOS boot options, we can browse the EFI and add custom items to the boot menu. So, if you happen to install windows second and lose the option to boot from clover, you can add a custom entry by browsing to *DeviceID*/EFI/CLOVER/ and selecting CLOVERX64.efi . You can name it what you like and set it as the first option so that you don't need to spam F12 to select clover. Note that the NTFS drivers are also needed for clover to boot windows.