In the import tool, we leverage import_id or constituent_id to control updates, why not also allow deletes? It is obviously up to the user to know how to first remove children records, etc. Global delete is not a straightforward option for normal deletes. For example, if we want to delete some custom fields (attributes). It deletes all of that particular custom field, not just the records in-use for that attribute type. That's ok for initial data loading but not a good system for general maintenances.
I've been focusing a lot of attention on using the address deleter plug-in before it goes away . . and wondering what I'd do if I ran into more addresses I wanted to mass delete. It seems like this Idea could be useful for that kind of a situation.