I would add a category of 'maintenence debt'.
Debt that appears as underlying technologies (like programming languages, libraries, infrastructure, etc) go through normal updates aka new version releases. Including deprecations.
This is debt that appears over time & no amount of careful planning can avoid it. And it snowballs if ignored.
I will look into adding that over the next few days. Great points ... can I quote your last two sentences?
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.