Invoke your local editor and edit the remote file. Additional benefits: no lag or delay in your buffer and editor, and you can save locally should the remote session crash.
(This presumes a direct SSH connection, e.g., no bastion host, though that can be addressed via tunnelled connections.)
Is copying .vimrc whenever logging in for the first time too much work?
Computers are perfect automation machines. Why embrace useless toil?
git clone https://my-dotfile-repo
ln my-dotfile-repo/.vimrc ~/.vimrc
This doesn’t hold true in 2022. People expect their settings to follow them around automatically.
One could make a command to check some central registry (or, what the hell, maybe a .vimrc blockchain) but typing that command would be about as much work as the curl/wget/git solutions proposed elsewhere.