In this example you're actually just being polite. You are not calling out a person publicly, you're transmitting a course-correction through their manager that allows the person who knows you best to communicate the correction the best way AND it allows the corpo to take the blame for being vague and uninformative.
Sure, direct, cold, concrete, public data is "best" in the objective sense, but people's feelings and pride matter, and any attempt to wave that away is just naive.
Schedule a meeting with the people you are directing it to then.
Blathering vague garbage execu-speak in a large meeting, even if it is some hare brained attempt to send "coded messages", is usually just some self-important charlatan bloviating and trying to sound intelligent and important to everybody else. And it is never effective communication.
Early in my career I tried very hard to "be concrete, cold, and direct" because that's what I thought a good communicator would do. It was seen as attacking to anyone below me and confusing to anyone above me. I was naive and I suffered for it.
I definitely agree with what you're saying here where these words actually do mean something, but it's completely opaque to those outside the "know". I also have found that there's not any better way to express information to those in the group than in this coded language, even if it makes completely no sense to me.
I wish younger me understood that the way I'm being perceived is the only important thing, not choosing the "best" words to technically describe a situation