I routinely ssh into my experiment at the south pole during satellite windows. I just use tmux on the other end...
On the "caveats", you need UTF8 support in the client machine, but today that's granted.
Still, mosh curb-stomps ssh on latency, input guesssing, data saving and bandwith usage.
Using that over 2G was a literal black/white difference compared to SSH which was nearly impossible to connect and the latency was unbearable. Under mosh I could chat, email, nntp (they still are some good newsgroups), IM over jabber/telegram, read news over RSS, code in C/TCL (jimsh) and read the docs with links, among reading books (novels and essays) with some CLI epub reading script.
Yes, I also used tmux on the remote machine too, mosh+tmux work great with each other. Albeit mosh resumes a potentially lost/dropped connection just fine (even without a running remote tmux/screen), I think tmux itself would send less data over the wire.
I was thinking about the route those packets were taking - from my computer to the plane router, up to a satellite, down to the DO data center in NY, from there to my home in NJ, then to the K8s cluster in NY, and then all the way back around. When you put it that way, one second per character isn't that bad.
Starlink does have some satellites in polar orbit (initially it seemed like there wouldn't be any, so this is relatively new), and there were some limited Starlink tests last year, but due to the CMB telescopes at Pole, which may be negatively impacted both by the satellites and the ground antennas, any Starlink deployment will be very cautious.