As it happens I've recently upgraded a 2 year old project with both node and C#
It was open much the same in both. If you're happy using outdated and unsupported components with security issues AND you can get hold of the right version of the dev tools and plugins AND your hiding environment still supports the old platform, you can maintain the old version with minimal change. But should any professional developer do this?
In domains where software is expected to run for years, if not decades, it's common to archive the entire toolset, along with libraries and SDK's in case you need to fix a bug/add a feature 10 years later. Obviously, in this case you can't have dependencies sitting somewhere on a server you don't control.
There are also situations where this is forced by regulation: you need to recreate build xxx.yyy.zzz 7 years after release because a customer reported a serious bug and it needs to be reported to the relevant regulatory agency and investigated.
I'm a developer (age 50+) rather than a data scientist and I've been lucky enough to enjoy all my jobs.
Partly I put this down to working at small companies where you have the autonomy to get things done without too much bureaucracy. However if I was put in a situation where I was working in a large organization and felt the job wasn't making the most of my talent, I would do 2 things:
(a) take my best guess of what I could do that was in my power that would have the greatest impact on the bottom line, and spend as much time as possible doing that (this might not have much relation to my job description)
(b) go as far up the management chain as necessary to try and get someone to understand what I was doing and why.
This maybe a naive and optimistic approach but I'd like to think that after you've tried this with a few different employers you'd find somewhere you were properly appreciated.
But if I can't understand why I should do that instead of something else I've thought of, then I'll do it my way thank you.