IMHO data integrity can only be guaranteed if you force it at the database level. Foreign keys in combination with cascade delete are one the best ways to do that. AFAIK almost all modules have a foreign key between the module data and the modules table (based on moduleid).

deleteing tables and recreating them is something that should not happen anyway :)

Handling foreign keys at core tables properly is more work, but not impossible. If a table change is done that needs a FK dropped temporarily and recreated after the change, that can be done... have a look at RedGate sql comparer.. they do it all the time