And that's where the question of empathy and compassion comes in.
As a random white dude, the "pain" I face by dealing with problems around these name changes is completely minimal and trivial when compared to the emotional pain they cause people in certain groups that actually have a lived experience of oppression.
Regardless, I do agree that if there is crazy scrambling and short timelines to change these names, that's a problem in your org. There should not be reckless urgency to get this done; it should be done just as any other major change should be: with planning and risk assessments. Where I work, we are doing it slowly and with an eye toward not causing downtime. If your org is not doing that, then I agree that you have a valid complaint. But this complaint should be directed at the bad process, not at the work itself.
Usually, when open source projects introduce a breaking backwards-incompatible change, they will first deprecate things and then wait some months to give people time to update. After this nomenclature had been in use for 10+ years, I can't help but wonder why there was no time to take the user-friendly path in this instance.
So to the people who are fixing the mess, it certainly feels more like you got kicked because someone else wanted to show off his/her moral superiority.
There existed a reasonable way to change the nomenclature, but it wasn't taken.