This should probably only happen on constraints with an explicit “relation” parameter (which would in this case be “subclass”). Otherwise we’d change the interpretation of existing constraints in possibly unintended ways, and also make them more expensive to check.

I agree with Lucas. We don't always want to have subclasses. We have a lot of crazy subclasses. I don't think https://www.wikidata.org/wiki/Q1415090 should be used at all. Someone has composer as occupation and might have been active in one or multiple field.

For painters we also try to prevent crazy intersections like animal painter. All clean now, see https://www.wikidata.org/wiki/Wikidata:WikiProject_sum_of_all_paintings/Intersected_painters . Take for example https://www.wikidata.org/wiki/Q247005 . That's not occupation landscape painter, that's occupation painter and genre landscape art.