Eh depends. I found myself in a situation where I was connecting to a changing set of servers quite frequently, which is why I built it. But perhaps I'm the outlier!
After having executed an involved ssh connection, my brain often opts to keep working on whatever I needed to use that remote machine for, instead of switching context and saving the details in ~/.ssh/config, even if I expect to use the connection details again.
So I understand the desire to manage both of those tasks, connecting and persisting, from one tool. I wrote a similar little utility that does this by adding a persist option to built-in ssh. https://github.com/emileindik/slosh
Reminds me of a little prototype I wrote a while ago that tried to do something similar with Javascript's Proxy class. https://github.com/emileindik/cashola
The main difference is that it stores the state of an object, not a function.
If your data is JSON serializable then it could be a cool way to save and resume application state.
I'm curious if people's qualms around abstracting the cloud/network also apply to the https://modal.com product. Differential seems like a similar project at its core, just focused on the Typescript + microservices ecosystem.