I think a lot of the whiteboarding/leetcode stuff is just hazing, a desire for "standard" processes (every candidate has a different background, so a well-done conversational interview will differ a ton per-candidate), as a bit of a time-filler ("that's right [C-suite person who's asking questions] we have very rigorous hiring, look, it takes six hours, and see all these steps! Only getting the best of the best, I assure you."), and because if it's scripted you can have mid-level devs do it—poorly, for the most part, since conducting a good whiteboard/leetcode interview is possible, so far as that goes, but it's not easy and requires serious people skills, which is a big part of where places go wrong I think, and also tends to make it look so non-cookie-cutter that if you squint it's not really that much more "standardized" than the conversational version.
Talking about those things is a learned skill just like writing on a whitebaord. Hence why good companeis that do whiteboarding interviews also have traditional rounds. You want to give candidates multiple avenues to shine.
A casual conversation where someone is purposefully trying to put you at ease is going to be more effective at seeing someone's true skill over a whiteboard every time.
There are also a bunch of very senior people that won't play interview games at all. Especially when they're an internal referral. If I refer someone to get hired, I make absolute sure that they are not put through a technical hazing ringer. I've seen senior people who were heavily recruited walk the instant they're put into "the process" under the very sound logic of: "You wanted me to work here, so why are you making this difficult?"