I don't have a similar answer for GMT/BST though.
That is exactly why I am enraged by "EST"-users out of season. Because they are deliberately insensitive to people who are actually in Standard Time.
But it actually seems to be deeply ingrained into American-centric corporate culture. I had a WFH job in a large company that was nearly 100% WFH, and they consistently used "EST" to their detriment. And I kept challenging this apparently-unwritten policy, and they just said "it's always been this way". And this month I've even caught UPS using it: yeah, the United Parcel Service was quoting transit times for one of my parcels in terms of EST, which was utterly nonsensical to me.
It seems that people don't mean "Standard Time" anymore when they write "EST" but simply "EaStern Time" and it is implicitly understood by human communicators to definitely not mean Standard Time except when it does. I went around with Gemini LLM about this for awhile. I cannot explain why people would embrace an obviously incorrect acronym, but they really have.
Honestly all this imprecision is because no standards body ever figured out a good way to turn the tzinfo codes ("America/Los_Angeles, America/Phoenix, America/Denver, America/Chicago, America/New_York"), which is what we are all actually trying to convey, into abbreviations. So we're stuck with identifiers like "-07:00" or "PDT" which have to be updated when the stupid time change happens.
Which is annoying.
However, the majority of the players on all the "oceans" (servers) converged on a different term for it. They called it "Game Time" or "GT" or "gt". I am unsure if this was a carry-over from common parlance in other games, or just something they felt more comfortable with using. I was not comfortable. People talking about "10:30 gt" was jarring and confusing to my neurospicy intellect. It surprised me, then annoyed me, then I had to mentally translate it back into "Pirate Time" and thus to "Pacific Time" as I was not in that time zone, and MST does not have a "constant offset" into Pacific Time.
So there was a case where the game admins prescribed, and adhered, to one standard term, and the players simply rejected it and supplied their own. So I do not know what "problem" was solved by that collective action, but mostly everyone seemed comfortable with it. It wasn't "wrong" or misleading per se because it was simply an invented acronym.
"EST" is wrong and it is not simply a preference to write the wrong timezone. If people like me, in perpetual MST, struggle to determine what offset is meant by "EST" then it's imprecise and misleading. We cannot merely say it's "descriptivist" and roll with it. Anyone who wants to avoid dealing with DST can simply write "ET" instead. Eastern Time. Easily interpreted, perennial, never wrong based on season or month.
But instead they've collectively insisted on co-opting an existing term and twisting it. Let's not be "descriptivist" in aiding and abetting misleading terms. Hopefully, if the U.S. completely bows out of Standard Time, something will change? I mean if we're permanently in DST, will corporations insist on sticking with their "EST" standards? That would be... bizarre.
We can though. Say EST out loud like it's a single word. It sounds like "east," as in "eastern." Next, pronounce all three letters: E S T. It still sounds like "east." This is why people use EST when they mean eastern. They aren't talking about daylight or standard time, they're talking about the time in New York.
No fair Googling anything! Good luck!
I suppose if I lived in a timezone where we don't switch between daylight and standard time twice a year I might have to rub two of my braincells together to remember if they "spring ahead" or "fall back" at the moment, but the entropy generated by that extra bit of recall seems trivial.