When I started working I went in with a plan to upgrade and modernize everything I touch. I still believe that to be the case, or like… my “purpose”(as an employee not a person).

I mean this with as much respect to you OP as I can possibly put into words, and if your therapist has already touched on this, absolutely ignore everything I say and listen to them.

I have been both been this person and dealt with this person. Believe me when I say that this behavior engenders little love from management and coworkers alike. You can quickly gain a bad reputation by trying to modernize everything you see. That reputation can be (meanly) described many different ways, from try-hard to kiss-ass.

• Developers like all human beings are subject to emotions and projection. They see you running around trying to replace the things they built, and they may conflate that with trying to replace them. They feel insecure, then they project that insecurity onto you - it makes you look insecure trying to prove yourself to the company.
• Managers begin to think that if they let you replace all their developers' tools, they will have to rely on you and you alone to support all those tools. They may worry you try to gatekeep your tools, or become a bottleneck for new development. So you slowly lose their trust.

Don't let your career suffer for this. There are few reasons to risk your reputation, your chance at promotion, the goodwill of your peers, and more: "using the latest and greatest" is not one of those reasons. Sometimes, following the crowd is fine.

Springboot apps, create-react-apps, codebases in c and c++, no kubernetes, little to no cloud.

Now, speaking as a developer instead of an armchair psychoanalyst, I don't see why these traits or lack thereof make for bad software. Nor does it make you a lesser developer for working with them. It entirely depends on your industry, the applications, the users, security interests, available recruitable talent, and many more factors.