As for giving talks that way, I would not say that qualifies as a high stakes environment. Your likely worst case scenario is that either your code or some bit of technology involved doesn't work right, so you laugh it off and explain what was supposed to happen.
The worst case scenario in a talk is that I say something stupid and get really dogmatic and defensive about it, leading the hundreds of people watching the talk to conclude that I'm an ignorant jerk, which, well, I can be, but I'd rather they didn't overestimate the frequency of that! I could lose face.
The worst case scenario in an interview is that the person interviewing me says something stupid and gets really dogmatic and defensive about it, and then they and their company lose face.
Oh, and they could decide not to offer me the job. But that's never been much of a problem, and it's certainly no big deal — if you're only interviewing for jobs you're almost sure to be offered, you should probably interview for more advanced positions. Not being offered a job is far from "losing out on a big opportunity", as you said in your other comment. A job gives you money enough to live on, but if you're a programmer jobs that pay a living wage are plentiful.
(But less plentiful if people go to your talks and decide you're a nincompoop or a scumbag.)
Oh, and if you look like a dogmatic jerk in front of an audience, there's nobody in the back row waiting to make a mark on your permanent record as a result, just so you know.
But, back, now to interviews. I've been in I don't know how many interviews (hundreds, easily, if we count both the ones where I was the interviewer and those where I was the candidate), and I can tell you for a fact that time pressure, performance anxiety, and every single other thing I've mentioned impacts people's interview performance, and does so in such a way that it wouldn't be relevant on the job. I could even cite research to that effect if you like.
For whatever reason, you're now so out of touch that it's absurd. I had a whole point by point refutation of every single thing you wrote here, because for the average individual, it's totally wrong, and it would cause them harm if they tried to incorporate what you wrote into their world view.
Maybe you truly don't feel the same type of anxiety in technical interviewers that most people do. Fine. The fact that you're (a robot, a Zen master, financially secure enough that having a job doesn't matter, a 99th percentile 10x programmer who crushes technical interviews with both hands behind your back and using the whiteboard marker in your teeth, or whatever it is that makes you feel this way makes you not qualified to give advice on the matter to typical, average people.
TL;DR: No. Just no. I can tell you're not going to convince me of anything, and I suspect I can't convince you of anything, either, but my conscience just won't let me let this go unanswered.
