AspNetCoreOData does not support custom routing convention?

We applied global routing mechanism in our Asp.Net Core application (you can find approach here). So, we specify some routing prefix that is applied to all routings. After that AspNetCoreOData stopped to work correctly - OData requests returns just json result but it is not handled in OData way. I debugged AspNetCoreOData code together with our ones and found that AspNetCoreOData extends IApplicationModelProvider with custom ODataRoutingApplicationModelProvider and starts manipulations with routings here. And it happens earlier (before we add global routing) than customization described by link mentioned above.

Does AspNetCoreOData team have recommended way to handle such situation?

And I see described issue like global one because approach with ODataRoutingApplicationModelProvider introduces a risk that officially recommended way of doing ASP.Net Core application customizations will be ignored. What do you think?