VCP driver for the Macintosh; late 2015

I guess you're chances are very small getting the monitor's Ethernet port working on OS X.
Probably you would need a modified kext - best place to ask would be the hackintosh sites - but you would have to be cautious with every OS X update as that could change the kext and leave you without working ethernet port...

You could however use one of the USB ports on the monitor to connect the Apple USB Ethernet Adapter for ~30$ and you're save.

You'd lose one USB port and 30 bucks, but I'd say it's better than the hacked solution over long time and you have an Ethernet adapter you can take with you, rather than carrying the monitor around ;)

Here is a method to hunt the kext which may cause you a hang system.

1. Boot in safe mode & make a capture of the minimal safe set of extenions loaded with:

   mkdir ~/tmp
   kextstat >~/tmp/safe.kextstat
   

2. Boot in normal mode & make a capture of the full set of extensions loaded with:

   kextstat >~/tmp/full.kextstat
   

3. Compare them:

   cd ~/tmp
   diff full.kextstat safe.kextstat
   

   and from this difference, which is including the faulty kext, extract the culprit by checking its installation date:

   ls -dlT /System/Library/Extensions/<extension_folder_name…>
   

   The faulty extension will be the one installed at the time of the start of your kernel hang.

   Beware: the extension_folder_name… is not the extension name as displayed by kexstat.

   Here is an example:

   on_my_mac$ kextstat | egrep 'Addr|ThunderboltDPA'
   Index Refs Address            Size       Wired      Name (Version) <Linked Against>
      70    4 0xffffff7f8125e000 0x8000     0x8000     com.apple.driver.AppleThunderboltDPAdapterFamily (1.8.2) <45 9 8 5 4 3>
   on_my_mac$
   

   is coming from:

   on_my_mac$ cd /System/Library/Extensions
   on_my_mac$ ls -dlT AppleThunderboltDPAdapters.kext
   drwxr-xr-x  3 root  wheel  102 Aug 31 05:39:06 2011 AppleThunderboltDPAdapters.kext
   on_my_mac$
   

4. Make a backup copy of the suspected extension:

   mkdir ~/Extensions_backup
   cd /System/Library/Extensions
   /usr/bin/sudo mv faulty_extension_folder_name ~/Extensions_backup
   

   and test this system with one missing kernel extension:

   reboot
   

5. If it is OK. You got the right culprit.

   If not. Just reverse step 4, reboot and repeat from step 4 to test the next potential extension.