Pine, please see the exact (quite precise) definition of https://en.wiktionary.org/wiki/technical_debt https://en.wikipedia.org/wiki/Technical_debt https://martinfowler.com/bliki/TechnicalDebt.html I.e. Technical debt is Not at all equivalent to "bugs". The topic is a tangential one. Software can work perfectly fine for end-users even if it has a lot of "technical debt", it is just a pain for developers to change anything in it or connected to it because the code has complex issues (it's a mess, or imperfectly architected at a higher-level, or "icky", or other factors). It is not possible to measure, and is somewhat subjective in nature.
Overall this thread is going in circles, and I recommend dropping it here. There are several good suggestions above if anyone wants to put effort into actual solutions.