Actually, I think there is a more expedient solution. All you need to do is support the INDI client/server interface (XML) to speak to a remote indi server that is running the drivers. There should be no other driver issues, and a bimodal SGP (INDI or Local Ascom) would be a killer solution.
In fact, while the INDI drivers are pretty mature for most devices now, there is also the INDI server for Windows, that is an INDI Server installed on a Windows system that is running ASCOM, and just bridges to the ASCOM drivers on that machine.
By doing this, the remote (scope side) system can be anything that is running an indi server, like a small widows/ascom laptop, NUC, or proprietary HW like a Kangaroo (ust for example). SGP can be ANYWHERE, connected via TCP/IP.
By Anywhere, this could mean at the end of a ethernet cable in ad hoc mode, that would provide far greater distances than the USB method most imagers use. Also, by using a small access point or router, the user can connect via wifi, or even the internet for connection ANYWHERE IN THE WORLD.
I own SGP and really like the tight integration, but if you compare this client server support to the new open source KSTARS/EKOS implementation, it would illustrate the proposed implementation.