I get your reasoning but still why use food terms for jargon in UX instead of something else.
Your example of a "P-trap" is good but its not like plumbers are going around saying, get me the "slinky hotdog" to bend a copper pipe, or you need a "banoffee pie" to seal this joint.
Why does it matter to you where the jargon came from? Why are vaguely shape-related jargon and military-derived jargon and acronyms okay but you draw the line at toast?
I would argue that FUBAR, P-trap, Dequeue, HALO are going to have a less likelihood of a context collision than borrowing an existing word that is ubiquitous in society.
For example in Google
"toast"
"toast menu"
"toast ux"
All yield different results
However "p-trap" gets you a narrowed list of results
"Platoon" turns up military answers until I specify traffic. And I'm actually not at all sure what meaning of "HALO" you're referring to—it must be jargon not in my vocabulary, but for me it refers to a thing angels have and to a video game.
Again, it seems like you're inconsistent in applying your frustration with jargon. You're frustrated with jargon in an adjacent profession to yours, but don't seem to apply the same logic to professions that are entirely unrelated or to your own jargon.
Your example of a "P-trap" is good but its not like plumbers are going around saying, get me the "slinky hotdog" to bend a copper pipe, or you need a "banoffee pie" to seal this joint.