For those unclear of the reasons this is bad (aside from the assumption that the pure raw data structure should not have any artifacts of custom data definition

For those unclear of the reasons this is bad (aside from the assumption that the pure raw data structure should not have any artifacts of custom data definition) - it is probably something in code or, more likely, initialisation data, that is expecing the Id to be something. This may be a file of SQL inserts that is run after the database is created, with hardcoded primary keys. This is an antipattern of course, but it doesn't excuse the fact that pure structure dumps should remain as such. (disclaimer - I have little experience with mysql, but have seen these same antipatterns in SQL server, oracle, and db2 data init scripts far too often).