Personally I agree with your opinion. While we're open to code audits with clients, it's not a scalable solution. We'll consider open sourcing the client code.
I understand the issue with a closed-source client. It wouldn't be trivial to open source at the moment, but maybe there's a path to do it in the future.
Sorry if it does not fit your business model, but in my opinion, it would be plainly stupid for anyone to download and run on his machine or server a closed source binary, especially when the goal is to give remote access through internet. And so that it is expected that this binary will open a direct pipe with the internet...
First, because if you are on a Linux distribution, you will tend to only take binaries from trusted sources like distribution repos that are imperfect but still audited and work on having reproducible builds.
Second because you can usually contained a closed source binary, let's say 'zoom' for example, but here the root goal is to open a pipe to the internet and give access to the console or local network, so it will be hard to check what it does and constrain it in normal operations.
Currently it's possible to provide your own servers to create a proxy-server cluster that's tied to a single account. In theory it would be possible to self-host everything, but I would imagine there are simpler solutions.
This is a side project I've been working on for several months with the help of a few friends. Please give it a try and see what you think. I'd love to hear your comments and suggestions.