The reason why it's removed before any such issues arise or become known is because Debian can't remove it afterwards - if they have included it in a release, t

The reason why it's removed before any such issues arise or become known is because Debian can't remove it afterwards - if they have included it in a release, they have committed to ensure that it's supported until the EOL of that release; and if noone upstream is supporting it, then it would fall upon them to provide these fixes. You can't simply remove packages from a release after it's shipped; either your release includes that package completely (including a commit to support them for the whole lifetime of your release) or not at all.