If I was going to use an alternate shell, it's got to have some solution for this problem that's transparent - something I can load into any sh/bash environment to get it running remotely.
I remember years ago mucking around with my home computing environment, making it so convenient, custom UI shell, monitoring widgets, highly customized bash environment with all sorts of fancy utilities that were just so handy, and all sorts of nifty features everywhere to tackle any problem I encountered.
Alas, the second I went anywhere else to do something--some friend or business's system, none of that underlying infrastructure existed. I lamented, "oh if only these other people followed my model I could just use X right now," life would be better.
At some point in my career I realized I was just wasting a whole lot of time customizing my native environment because those features were non-portable and the more I dealt with working in other people's environment, the more I realized I should just focus on learning the best way to do things in the popularly adopted environments because it meant my knowledge transferred almost everywhere.
I don't even really change the wallpaper on a desktop anymore, feels like polishing a hammer, a waste of time.
I wish you could carry your environment around with you, but I don't see how it could possibly work that way neatly.
An exception is that I usually end up installing a lot of stuff on Windows desktops to make them vaguely usable and scriptable, but Powershell and WSL will probably eventually mean I give up doing that, too. The previous sentiment was really about UNIXy systems.
It won't immediately solve the problem, but it can eventually. It can be the default and only shell on a Linux distro, whereas shells like fish can't, because they would make the system non-POSIX.
Or even just a script which could quickly bootstrap a shell and dotfiles on a system.