So turns out you can use a standalone C++ interface mapper called Gopher 360 (search on git), run the exe from cmd and it will generate a config.ini file with your default bindings, which are all what you'd expect them to be. Left analog controllers mouse, right analog is scrolling, B is left mouse click, Y is right mouse click, A is enter, X is toggle console. + is windows key, etc etc.
So with that, control of desktop interaction from the switch's SCP xinput emulation is possible, Second issue is, of course, the notorious phantom pointer that Windows 10 is known for causing in remote desktop and streamclient APIs. Only work around I've managed to find with this, is if you go into your mouse pointer settings and enable default pointer style, with pointer shadow enabled, and then also enable 'pointer trails' under the 'Pointer Options' tab of Mouse Properties. I'd just make the trails length as short as the bar allows or else it leaves mouse artifact afterimages all over the switch screen from bitrate lag.
In any case, with that enabled, the mouse pointer is visable on the switch, and desktop control and game launching becomes a reality. If you plan to do any light browsing or anything of that nature though, I'd deffiently quickbar the windows On-Screen Keyboard. Typing on it is a real hassle though.
Sidenote - left analog mouse sensitivity can be adjusted from high-med-low with R+L on the joycons. Low is most practical given the acceleration the analogs seem to invoke.
annnnd with that, i can now enjoy my collection of pc ported interactive VNs from my switch wherever in the house i feel like propping my feet up. Marks for a happy day indeed. Thanks again for bringing such a vastly utilizable brew to the scene, gents. You're doing god's work. xD