OK, if the second notification simply isn’t firing under that usage, that would more be a case for filing a radar with Apple than an OpenEars bug (if you feel that that is an interruption in Apple’s sense of session interruption, and not just a change of application like switching to another 3rd party app would be).
I won’t do anything opinionated in didBecomeActive since that is definitely app logic and not framework business logic, so I would probably recommend carrying on with your workaround.