Revit visibility graphics seem to be based on type representation maps, not instance classes

Intuitively, users changing visibility graphics settings expect that if they disable a category (e.g. walls) then walls, and only walls, would disappear.

However, this seems not to be true.

Consider the scenario:

1. IfcDoor X has IfcDoorType TX.
2. IfcBuildingElementProxy Y exists.
3. IfcDoorType has a representation map of Z.
4. IfcBuildingElementProxy Y also uses representation map of Z somewhere.
5. IfcDoor X imports into Revit as a Door category.
6. IfcBuildingElementProxy Y imports into Revit as a Generic Model category.
7. User toggles visibility of Door category.
8. Surprise! IfcBuildingElementProxy's Generic Model disappears.

In IFC4, considering the where rules for typing, the scope of this problem is reduced. However in IFC2X3 this is a situation.

Start by reproducing the IFC2X3 scenario described: share representation map Z between an IfcDoorType and an IfcBuildingElementProxy, import into Revit, and toggle the Door category. Trace how representation maps and Revit categories are associated; done means hiding Door elements no longer hides the unrelated Generic Model element.

Written by the indexing model from the issue text.