Please, excuse the inconvenience, that the lack of such functionality, may cause your team and you.
Moreover, when it comes to MS Windows and no active desktop session, the OS does not "draw Window" objects, so there is nothing for the "Mouse" and "Keyboard" to interact with. This is how headless browser test execution will be affected by OS limitations similar to these, which affects the test execution in an inactive desktop session
. So, having a browser in UI-less mode is useful for JS unit tests and not for functional tests, which should verify how the web page behaves in terms of visual representation like dialogs, windows etc. And having all these specifics in mind, claiming that Selenium "works", simulating real user behavior in headless browser, is just not true.
I hope these details will be helpful for you to understand the concerns and limitations in front of Test Studio team in regards the headless browser support.
Thank you for your understanding in advance.