I feel that! 
I, too, had self-selected to csh (and to emacs) back in the 80s, and fought the good fight dragging customizations and habits with me well into many versions of Mac OS X.
At some point, though, I succumbed to bash in order to work with peers, advise clients, and supply them safe/portable scripts.
I only come into regular contact with tcsh through my last lingering TrueNAS Core server. (I’ve not upgraded to its sunset release, wherein even baseline FreeBSD finally switched to ash to end this generational confusion.)
With both Debian and macOS now defaulting to zsh, I’ve finally found a home that I consider worthy of nontrivial customizations again.
If I still felt enough energy to hold back the tide affecting every single system I use, I’d probably have long since embraced fish.
So again I do very much recognize the appeal. But I suspect that the right balance is that the base appliance hypervisor should not carry tcsh as far past its due date as TrueNAS Core did.
Instead: I’d heartily encourage you to install it into any and all Containers workspaces where you set up your own camp. It’s in those environments where you’re the exclusive admin; where each of us is free to install packages and decorate our nests with all of our own personal creature comforts. 