I’d try to explore the ionicHistory flow.
For me it’s ok that every single tab have a custom history and you can navigate into the stack of the single tab example state TWO. But if you go back in the stack of the tab TWO you could go to the back View that is the state ONE in History ONE.
I had follow the flow and when the stack is at the last View of the tab TWO in the back view there is correctly the View in the state ONE but if you call the method backView.go() or IonicHistory.goBack() there is a strange behavior.
I have one HistoryID for tab TWO and one HistoryId for state ONE the last view on the stack of history TWO have a backView in the stack of history ONE.
But if you call the method above the Ionic framework create a new HistoryID with another view that is a copy of last View in History TWO and have a back View that link to itself “last View in History TWO”.