Minimizing Risk of Attaching USB Controller to dom0

Hello, I am trying to setup a second monitor for my device. The device’s native HDMI port is attached to the dGPU which I passed through to a VM and is thus unavailable to dom0. I have purchased a USB-A to HDMI adapter to enable me to use a second monitor, however, I am unable to attach this device to dom0 from sys-usb. To my understanding, this is by design and cannot be bypassed and instead the entire USB controller must be attached to dom0 as per this discussion. As it has been a few years, I was wondering if there were any additional guidances, new tools or developments, etc. which may be applicable and which may help insulate dom0 from any potentially harmful device firmware.

As an aside, I am aware the GUI layer may optionally be managed by the sys-gui layer which seemingly would allow me to maintain dom0 isolation and still install and use the firmware for the monitor. However, I haven’t found sys-gui to be workable for my needs and setup.

Thanks in advance for any responses and help.