I think checklist interviews miss the mark as you say. You may not have a perfect rubric, but I’m not grading students on a history exam; I am evaluating them for a role in a given position. In the limited time we have to speak, I want to use my intuition and experience as an interviewer and engineer to rapidly get to where the candidate is strong, and where they may have issues.
Does it sting when I get a "No"? Yes, a little, but I did my best and (presumably) someone else did better. So, I take solace in that I did not have to make a (relatively large) decision.
How the heck do you measure actual performance? Income / promotions / etc is very frequently a horrifically biased metric, for similar reasons to interviews. It seems like there's a pretty good chance they're just measuring relative bias between interviewers and the interviewee's management, and concluding interviews are done poorly when they disagree with management.
I don't think management is in general a good measurer of technical skills. So the research seems to be pushing for "interviews that force you to think like a manager" rather than "interviews that find skilled individuals".
As soon as people figure out the check boxes or the structured pointing system they start to check all the boxes, but it doesn't necessarily speak to the nuances between individuals that make them diverse and both valuable. In fact it can lead to a certain type of person people hired or promote, which can be on good characteristics, but I find many times turns into a "certain type" of person.
I guess what I'm saying is structure can take you so far, but you have to be willing to explore a little bit about what makes a person special, and that many times means not controlling the whole interview, and be willing to have your bias challenged through the candidate directing some of it.