Using QRQCs for Bug Detection

I have read several QRQCs and generally, they pertain to "hard to detect" bugs. Either they arise from specific uses of libraries (in which case, it's logical to include them in the database), or they stem from interactions between multiple components plus a difference between the Acceptance Criteria (ACs) and what the developer intended to do (an example would be a ticket for managing deeplinks that doesn't display the correct page if the deeplink is not recognized). However, I think there are detectable issues. For instance, I read about a bug caused by a too-short longPress duration. This is detectable, and we could include a message like: "A recommended duration for long press is 700ms for accessibility reasons."

Similarly, I believe there are bugs that are caught in code reviews but could be detected directly during the development process. Therefore, QRQCs are generally hard to leverage, as they usually represent the most complicated bugs to catch and require a deep understanding of the interactions between libraries, multiple files of the project, and the specifications (ACs of the tickets).