Indeed, there is such flag, but it's not fully tested in all the possible situations. It's there for a fallback in case it's really needed, but it doesn't use a complex solver to check the deleted database objects tree.
But we can try to investigate and see if this can be improved at least in your case. Do you mind adding a feature request for that and attaching a sample project reproducing the issue of this specific case so we can try to improve it?