Wondering if my suggested K2 Migrator improvement is a possibility?

In a previous ticket I mentioned an idea that I probably should have put in it's own ticket. I also created an entry in the features request. I keep hoping to hear from Mark about whether this suggestion is something that is possible to add to the K2 migrator or if maybe it is too much work and not worth the effort.

Sorry for opening a new ticket here but I am anxious to have a reply because it will help me to plan accordingly since I have a site at https://www.drcarney.com which has many hundreds of K2 Items many of which have quite a bit of data in extra fields. I would like to import all of the K2 Items into EasyBlog. Here is the text I placed in the feature request:

I just made a copy of my site onto a test site and then used the K2 Migrator to import all my K2 items into EasyBlog. I was truly excited to see what a good job the Migrator did.

Unfortunately there are a couple things that the Migrator did not do which I need for this site and one other site that I want to import K2 content from into EasyBlog:

1) Subcategories:
All K2 Categories and Subcategories were imported but the parent to child category relationship were lost during the import. So, ALL categories ended up in the root level. I think that the Migrator needs to keep the parent child relationships for the categories and subcategories from K2.

2) Extra Field Groups:
None of the Extra Field Groups from K2 were brought into the EasyBlog Field Groups.

3) Extra Fields:
None of the Extra Fields from K2 were brought into the EasyBlog Field Groups

These are the three things that I believe need to be added to the K2 Migrator.

Is this something you would consider doing? I think it would be a great improvement to the K2 Migrator.