I think that the behavior that you are describing is working as designed. The Explorer Inheritance setting is used to determine which classes to show in the tree, and not which rules appear under which classes.
To give an example I configured something similar. 2 Data classes, one called ParentData and one called ChildData. ChildData is configured to directly inherrit from ParentData.
With Pattern Inheritance I do not see the ChildData class in the App Explorer tree when looking at the ParentData class, but with Directed enabled I do see it (see the screen shot below).
I guess what your users are expecting to see is the ParentText1 property showing up under the Property group for the ChildData class. I believe that this would be an enhancement to the product (e.g. an additional show inherrited rules option). It may be a little confusing to have ParentText1 show up under the ChildData class if it is not really defined there. In the second screen shot below it would then appear twice, once under ParentData - Property and once under ChildData - Property. I guess it could appear greyed out or something to indicate that it is not really part of that class.
Show inherited properties is going to be a very useful feature in our situation, because most of the business entity related properties are defined under the parent class, only a few properties defined under the child class to handle presentation layer UI/UX issues.