Noticing the issue in the first place is the big problem, as TFA says the side effects of this are likely graphical glitches that would not stop any shows and just get marked down as a hardware timing issue¹. Once noticed by someone with the skills to notice it while looking at the code for other reasons, it is obvious².

Proving the fix fully resolves the matter without adding others could be a detailed task, perhaps with multiple skilled people passing their eye over the result to try ensure there isn't another “oh, interesting” moment³ waiting to happen, but again doesn't necessarily mean needing to reliably simulate the exact situation.

[1] pick up another couple of devices, yep confirmed, it doesn't happen on these

[2] well, obvious to that someone with that skill, I'll not claim it is as obvious to such as myself!

[3] like one that may have been how this was found, assuming it was spotted in passing while working on that area for other reasons