Resource doesn't appear in catalog if controller is not named per convention

Have a resource named LocationTagResource, but controller cannot be named LocationTagController due to naming conflict with core. With name of LocationTagRestController, doesn't appear in catalog.
Peeking at the ResourceDocCreator code, it seems like a limitation (i.e. bug) there, where it tries to get the resource name by convention rather than looking at the BaseCrudController<ResourceName>