If I'm a chef, and I have two line cooks, each with an onion, and I tell them that their onions will need to be prepared for French onion soup, and I order them to caramelize their onion, and one comes back in 10 minutes and the other comes back in 45 minutes, I am going to have a long conversation with them about how words having meanings.
This isn't a random context, this is the context where the term "caramelize" is technical jargon.
(Imprecise language bugs the hell out me as well, but it seems like it’s easier for me to bend than to attempt to fix all the humans.)
I can be mowing my lawn when it's 110F outside and say, "Gosh, I'm boiling." But if a recipe tells me to "boil" something, and it means anything other than put it in 212F water with heat applied in such a way that the water is bubbling, then the recipe is a shitty recipe, and I will diagnose the author with a confusion of the mind. The fact that the term now encompasses a much broader range of meaning in other contexts is completely irrelevant: I am not in those other contexts, in this context, it is a word with a very specific meaning.
You have a point here, there is a "context collapse" happening, when this definition is necessarily precise for professional chefs, and less so for "people who cook to eat".
However such recipe books typically claim to bring some of the professional techniques and results to the home cook, and as such are sowing confusion if they encourage "semantic drift"
https://interparestrust.org/terminology/term/context%20colla...