Earlier quoted context omitted.
Not necessarily. The technical people managing the repos might just be opposed to name changing in general (seeing how a boatload of links, references, documentation would require updating, some of which you don't even control), and meanwhile those people might feel the "misbranding" drawbacks much less (if at all).
I would categorize all those as emotional reasons not to change, not logical reasons. "It's hard!" So? "It's complicated" So? "Some of it other people control." This will always be the case, you can't let the perfect be the enemy of the good enough. If the status quo means a worse project, then you're not changing because you don't WANT to, not because it's a good idea. And that's an emotional, not logical ,decision.
My point is that from a developers PoV, renaming is not an evident net-gain at all-- might be seen as pointless branding busywork that leeches ressources from "actual" problems.
That is not "being emotional", it's just different priorities.