iD "Map Features" filter behavior for "boundary=protected_area" zones

[Zyolix]

I'm a frequent mapper for several years now and my primary area of interest are hiking-trails (or tracks that can be used for hiking) and the landuse along those (hiking) ways. I usually record my tracks and take digital notes when hiking and afterwards enter my findings at my home PC using iD.

There is one single behavior of iD which occasionally makes OSM-editing much harder for me than it needs to be. My hiking trips and OSM-editing afterwards regularly touch "protected_area" zones which are already recorded in OSM. I'm not an expert on this "protected_area" matter and not interested in those objects (from a mapping perspective) and neither want to see nor want to accidentally touch or modify them.

Nevertheless, the iD "Map Features" filter design currently covers these "boundary=protected_area" zones under the "Landuse" filter rather than under the "Boundaries" filter, so I'm forced to see and pay attention to the "protected_area" boundaries if I want to see and edit the landuse structure. This is IMHO illogical since "protected_area" zones are invisible virtual objects similar to administrative boundaries and not physically visible objects like forest, farmland and water. Boundaries of any kind are usually chair-mapper business and not relevant for OTG-mappers. OTG-mappers should be able to configure an editing view which just shows OTG-objects.

The attached screenshot shows an example of the potential display clutter when physical landuse and virtual "protected_area" boundaries overlap. It is cumbersome to identify and safely edit the landuse structure without accidentally touching the "protected_area" objects.

I would like to suggest changing this behavior and showing/hiding the "protected_area" boundaries based on the "Boundaries" filter setting rather than based on the "Landuse" filter setting.