And this will go on for many, many steps. And when you finally get to the end of it, they'll say "sorry, you'll need to replace this keyboard, and it's out of warranty, so you'll need to pay for it yourself" and you'll have spent many hours over a period of weeks just to get the answer that you were 95% certain you were going to get in the first place.
It is true that they were out of warranty and couldn't reasonably expect a free keyboard. It is true that your support helped them identify that the keyboard was the issue, so it was a successful diagnostic in some sense. But the experience for the customer is super terrible and infuriating.
What would you want as a customer in that situation? What I'd want is to get an email like "Hey, I'm really sorry you're having that problem. As you probably know, you're out of warranty. There's a pretty good chance that you're going to just have to replace the keyboard, but if you're interested in trying to debug it to make sure the keyboard is the problem, we're happy to work with you on that." And then if I did want the debugging, I'd love to get a single document containing the debug steps that I could work through in one sitting.
That's why I think your insistence on "let me see your case to identify if any steps were done wrong here" is off-point. The problem isn't any particular debugging step or any individual case, it's that your whole process is fucked and customer-hostile in its conception.