you may already be aware of this but the mdm log will give you a blow by blow account include tables/columns changed/dropped see C:\WINDOWS\Temp\MetaDataManagerLog.xml. it will however only have the data up until the failure of the mdm changes to the database.
It's pretty hard to do this as every site tends to have different objects/indexes. The best I've managed is to turn database trace on before running MDM. The trace produced has a lot of stuff in it that isn't in the metadata files, but even so each sites contents will tend to change..
How about dropping all the stats? There is usually a naming convention that would allow you to spot them. As MDM recreates all the indexes, I suspect the value of any remaining stats would be quite low.
I also thoroughly recommend a VMWARE DB server with a snap shot making it a bit quicker to get back to where you were? (But you're probably doing that already)