Looks like a bug... I'm not sure we have a unit test to cover this scenario, so I'll have to step through it and verify. 

Yes, this is a known issue and will be fixed within the next official release.

Since I had a backup of your database, I restored it and then started testing the DDT import.  The reason all of your data types were incorrectly imported was due to the user-defined data types, which the DDT doesn't support. So I changed the import to test for this and instead of returning an Integer as the default, it actually extracts the underlying data type from the User-Defined definition so that the type actually comes into the DDT correctly.  This will be included in the post I put out there at the end of the day.