Magento 2. Data Migration creates new attributes sets for default magento attribute sets

Nobody has claimed this yet.

Preconditions
PHP 7.0.20
MYSQL 5.7
Magento 1.12.0.2 EE >data-migration> Magento 2.2.2 || Magento 2.18 CE

Steps to reproduce
Migrate data using data-migration-tool for above mentioned versions

Expected result

Attribute set with given attribute_set_id,entity_type_id, attribute_set_name combination(from source) to map to existing destination attribute_set.
To be more explicit I expect that default Magento 1 attribute_sets to simply map to default Magento 2 attribute sets and not duplicate.

Actual Result
Default Magento attribute_sets are duplicated and Magento 1 attribute sets take the existing Magento 2 attribute_set_ids.

I'm not sure if this a bug or a feature.
If this is a feature what is the reason behind it?
What am I supposed to do with the duplicated attribute_sets
Migration_Default attribute sets take Magento 2 default attribute set ids so removing them is not an option as Magento 2 hardcodes attribute_set_ids in core code.


Start with the data-migration-tool migration described in the issue using the stated Magento, PHP, and MySQL versions, then compare source and destination attribute sets and their IDs. Done means default Magento 1 attribute sets map to the existing Magento 2 sets without duplicate sets or replacement of the destination IDs.

Written by the indexing model from the issue text.