I think you're missing the point. Perhaps you're new here but at no time does GL.iNet ever disclose their SOHO routers are reliant on closed-sourced/proprietary SDKs like Qualcomm's until you start poking around in this forum. They go to great lengths to make great fanfare about running OpenWrt, however. Once you scratch the surface only then does it become apparent in the the glaring oversights, omissions, misconfigurations, choosing to focus on idiotic feature requests instead of addressing their bloated tech stack.
So now they're doing no better when it comes to the KVM side of things. How do you expect to pass a security audit when you can't even control what servers your devices/infra is dependent on? You better hope you can grep for a conf to edit out that STUN string & hope it's not baked into the binaries.
JetKVM is built with Golang & dev support in mind. That alone places it above the Comet... but I'll be damned if the upcoming Comet Pro's hardware isn't worth hacking the hell out of to get it into a usable state.
TL;DR: I'm sorry you bought the Comet v1 but I didn't make you open your wallet.