WTH doesn't Cover have more device classes

As things stand, none of the device classes supported by Covers reflect the semantics of projector screens or awnings. E.g. devices that are “open” when they are not retracted. All of the existing device classes assume that the Cover is open (or not covering) when it is retracted - e.g. like a blind or a gate.

I see many requests for the ability to “invert” the cover (and many solutions to this using templates) but that isn’t sufficient for the front end widgets to correctly reflect the state of the device. Either the arrows point in the wrong direction or the icon doesn’t correctly reflect the state.

I did submit a PR for this but it was rejected because it was a change to a core component and an architectural proposal had not been approved. I also submitted an architectural proposal but it hasn’t gained much traction. Nor has this similar proposal.

If anyone agrees with this idea then perhaps upvoting or commenting on the linked proposals and/or this discussion might help with getting it implemented?