I didn’t say it was unobtainable. But it might look/behave quite different than the tools you are currently using.
As for Microsoft Exchange, I only use that for work, and my employer would not allow me to connect from my personal machine anyway. I am not saying that you that you have to give up your favorite tools… but I am saying that it you are putting up so many fences then you might as well stay with what you have.
When you come across some Python code for something written 5 years ago and they used four contributed packages that the programmers have changed the API on three times since then, you want to set up a virtual environment that contains those specific versions so you can at least see how it worked at that time. A small part of this headache comes from Python itself mutating, but the bulk of the problem is the imported user-contributed packages that multiply the functionality of Python.
To be sure, it would be nice if those programmers were all dedicated to updating their code, but with hundreds of thousands of packages that could be imported written by volunteers, you can’t afford to expect all of them them to stop innovating or even to continue maintaining past projects for your benefit.
If you have the itch to fix something old so it works in the latest versions of everything, you have that option… but it is really hard to do that if you cannot see it working as it was designed to work when it was built.