On macOS 10.14.6 (2017 MBP with i7, DisplayLink running on i-tec USB-C hub), DisplayLinkManager takes up to 5-10% when supposedly idle. When running audio software - namely, Ableton Live and Reaper, but likely this can reproduced on any audio software and DAW - DisplayLinkManager can take up to one full core (~95% CPU reported). This doesn't seem to be related to the size of the project, so even small projects that take up 15-20% CPU are massively affected by this issue.

Native Instruments Kontakt has an even weirder behaviour:
- restart MBP
- connect external monitor via DisplayLink
- try to run Kontakt (actually, ANY NI app, including Komplete Kontrol, Maschine and Creator Tools). The icon bounces in the dock and the app doesn't start at all.

Oddly, if you run Kontakt BEFORE connecting the external monitor, it will work fine. If you quit Kontakt after connecting the external monitor and relaunch it, it will open just fine. This issue only happens if you open Kontakt for the first time in a session while having the external monitor connected.

DisplayLink is currently unusable in a real-world music production scenario. Please fix!

Further details:
Focusrite Scarlett 6i6 audio interface. CPU drain increases by around 10% when using external USB audio interfaces regardless of their manufacturer/drivers, which is unacceptable but seems to be only part of the issue.
Tried to remove all the peripherals connected to the USB hub to no significant improvements
Using HDMI port, only one display connected
Tried on and off battery power

On Mac Mojave, Displaylink does not support HiDPI resolutions. These are screen modes that render the desktop at double the size so that fonts become more crisp. For example on my 1440p monitor, there's a 720p HiDPI mode. When I connect the monitor directly to my mac, this mode can be selected. When I connect via my Dell D6000, nothing happens when selecting this mode.

You can use the following open source application to select resolutions:

https://github.com/chris1111/RDM

A related issue is that custom resolutions added by the above application do not work when the monitor is connected via Displaylink - but do work when the monitor is connected directly.

Having recently upgraded to High Sierra on a Mac that can't use Mojave I am now stuck with a completely useless Asus MB16AC that was supposedly enabled for use on Mac by your driver.
Your supposed "fix" of extending via Airplay doesn't work. In Preferences, even when DisplayLinkUserAgent.app is enabled under Accessibility in the Security tab, when you got to the Displays Preferences the Airplay Display setting cannot be set to DisplayLink ("Could not connect to DisplayLink") and -- crucially -- the Arrangement tab of the Displays dialog does not appear! That leaves the MB16 stuck in mirroring mode, which is of no help (why have an extra monitor showing exactly what's on the main monitor?).
If you claim to offer a workaround, aren't you duty-bound to check that the workaround itself actually works? People relied on your driver when making their purchases, thus you are responsible for making it work as advertised, or at least coming up with a workaround that actually works. Anything else is unethical and unacceptable. Please, fix this now!