So with that context, my take is that while I'm very sympathetic to wanting a short and pithy description, I do think that the chosen terminology really does fail to intuitively encode the full intended definition, and that's on the definers.
Is it though? What about farming? Does each farmer get to decide what "organic" means? Does every shoe manufacturer get to decide what "Ethically Sourced" stands for? I'm not so comfortable with the argument that "well, it means whatever the hearer wants it to mean, and if they get it wrong that's because it was defined badly?"
I don't think "Free Software" is a terribly intuitive term (and never has been.) If anything the intuition seems completely tangential to it's actual meaning. But if you choose a FSF License, then you are releasing code under that license.
"Open Source" is a somewhat better name - but again open to misinterpretation. "Open" to whom? Everyone?
But for a -company- (and make no mistake, we're talking about -companies- altering the "popular meaning") to change the meaning so that it dilutes the actual meaning, and makes companies more powerful, I feel is not ok. In that context Open Source means something. Whatever they "intuit".
I think your other examples are indeed examples of the same kind of issue. For instance, I would say that "organic" is a much worse offender due to it targeting a much larger audience than our computing jargon does. I don't know whether "ethically sourced" has a technical definition that is a good match for my intuition of what it means, but I wouldn't be shocked at all to discover that it does not.
But like I said, I'm sympathetic to the definers of these kinds of things. They want something that works as marketing, so they use plain words that people have positive associations with ("free", "open", "organic", "ethical"), but then those words are too vaguely defined for their purposes so they also attach further meaning to them. But then that results in this tension, where people naturally assume the words mean only what they mean, and some community of gatekeepers has to be vigilant to come in and set the record straight.
Notably, we don't do this sort of thing with medicines, for instance. There isn't a community of people who have to correct peoples' use of a descriptive plainly worded jargon term like "happy pills", they are instead referred to as SSRIs, which has no plain reading and thus no potential for confusion.
I agree that it isn't good for companies to take advantage of this plain reading / technical definition mismatch, but I also think it's inevitable when trying to have it both ways by using a plain-sounding term while attaching it to a technical definition.
There's one cohort that grew up in the 80's and 90's, and so "were around" at the dawn of the FS / OSS movements. We saw the evolution of Linux, Windows, MacOS from the beginning, and understood the fundamentals.
A later cohort has grown up in a world where all these things are mature, and phrases like "Open Source" are less clearly understood. They may not understand what the term actually means, and may use it incorrectly (and more importantly the community around them uses it incorrectly) and so the incorrect version seems to "be the right meaning". It can be confusing when the term you think means one thing, ends up meaning something quite different.
In the way that a lot of people see "Free Software" and assume that's free as-in price, not Free as in restricting-people-from-users-accessing-source-code. Even those well versed in Free Software don't necessarily understand the "users" part of that sentence.
In the same way "Open" means different things to different people, and that may or may not match up with the -actual- meaning of the term Open Source.