When I worked as an independent consultant I'd get clients who needed fast turnaround on designing new feature architecture to a product I had not seen before, which is the closest analogy to the interview whiteboard design that I've experienced.
Even then, it's completely different. I'll first spend a couple hours with someone senior who can fill me in on all the relevant context. The dynamic is different because they need my help and are paying for it so they are highly motivated to give me all the context I need to help them. Only after that we go to the step where I whiteboard a few proposals and then we collaboratively decide which way to go. I'm quite good at this.
Interview whiteboard design is a different skill entirely, one which I don't believe has any relevance to job performance. Might be a good way to hire improv theater actors, but not engineers. Having to go from zero to solution in 45 minutes or less is not how it works in the real world. And doing so while being nitpicked by an interviewer more interested in showing off doesn't help. Instead of collaborating, the interviewer is there to grudgingly drop the occasional hint and then count it against you.
None of these interview practices are by themselves good or bad, it depends on what the actual job will demand.