There is also a difference between an experienced industry hire - as you say, if you've been doing this for 10 years you can go into an interview and show them a pretty good picture of what they are getting - and a less experienced or campus hire, where what is important might be an expression of potential - the practice helps with letting the interviewer see that, if your interview is the first time you've tried to code at a whiteboard, or solve a problem with someone trying to push you to the edge of your comfort zone, then you are doing yourself a disservice.
I have, however, encountered candidates who just didn't know, they didn't go to a top school (or indeed any school), they haven't worked in this environment, they don't have any understanding of what to expect - even the simple web-search that would have warned them requires some level of a priori knowledge - not every candidate has that - I suspect most of these candidates do badly, but just watching how someone learns through a day of interviews tells you something, that higher level bit about learning when in over your head is one of the most valuable.
Or maybe it's confidence? I don't know. I've been programming professionally for over 10 years. I think I should be able to sit down and work out almost any problem in an interview.
I've definitely been to interviews where I ran into issues and didn't get offers, but I've also been to interviews where I ran into problems and did get offers.
I guess, in my gut, I feel like studying for an interview is cheating a bit. It might not be the right outlook, but it's something I can't shake.