Hello,
Thank you for the detailed report.
This proves the device doesn't appear on the USB.
There is no amount of trickery on the driver which would make it work as it is now: the driver is not even invoked by Windows as there's no device on the bus.
DisplayLinkManager log is created when the driver starts, not when it installs. The installation is visibly correct in the setupapi logs.
I can see two possible sources here:
- interoperability issue with the host controller of the NUC,
- power problem.

The last experiment I could suggest is to try in USB 2.0 mode via your externally powered hub.
This is WAY out of the USB specification for the power, but you'd be using a totally different path which is somewhat less prone to interop issues.

It is possible you would have to remove all elements of the j5create/MCT. Some elements may need to be removed manually if reports from other users of that competitive technology are correct... and I believe them.

Kind regards,
Alban