Update
I want to give a quick recap on my experiences with this.
What We All Really Want is Internal Development Platform
What are Internal Development Platforms (IDP)? Well, this https://internaldeveloperplatform.org/
In my own words, it's what I'm trying to do. I'm trying to build reproduceable, idempotent developer environments for any use case. We used to all develop on mainframes, then we moved back to developing on our local machines because VCS. Now we're back to developing on huge behemoths while thinking we're on our local machines. It's great. Anyway, for IDP, we do not SSH in. We tunnel. I get that is essentially the same thing. The important part is it's not manual. It's seamless. We don't know we're not on our local machine. Even our files sync.
SSH Is not the Answer
Now that we know what I am trying to do, we see SSH is not the right approach. What is the right approach? Coder. What is Coder? https://github.com/coder/coder
It's essentially, what we've all been using. Be it VS Code or IntelliJ or Jetbrains. The IDE we've been working with uses the same basic stuff under the hood. The aesthetics are different, but they're basically the same. Coder is what lives under all the fluffy stuff.
The premise here is to run coder as a server platform, and remote to it with whatever IDE we use on our local machines (even our tablets).