The Jira complex state table tends to be something that isn't replicated as its part of the "we're not Jira" value proposition.
Your case might be in a "Closed" state on the UX, but internally that can be "custom state 48083232" because some wingus decided to first start by naming it "to be closed" and then changed it to just "Closed". That can be different for every project.
This is why an import tool is a complex thing to figure out. You have to translate all the potential custom states into the "we're not Jira"'s states that make sense.
The only "oops" part of the Great Import was that the users that were in Redmine but not in Jira (people who left the org and thus were never imported into Jira) had entries created as the sysadmin who ran the import.
This is the problem. Jira is so highly configurable that without recreating a good chuck of the Jira feature set, an "import" tool will be pretty hard to make.
Any competitor in this marketspace will have to invest a considerable amount of their time creating and maintaining such a tool, which I imagine if they ever became a serious contender, Atlassian would put up some anti-competitive road blocks. (For example, forcing everyone into their cloud offering so they can more easily control endpoint access....)