I think that's a perfectly reasonable alternative name.
It's needed for the RawRepresentable conformance. We don't have anything to match in-memory representations with, so it's not adding as much signaling value to this type as for other types that follow this pattern. But, given that it's frozen, I don't feel that we should go out of our way to hide the raw value.
It would land us in a similar position. From an aesthetic perspective, it feels a little off as this has nothing to do with Objective-C. Practically speaking, I think it would add a synthesized trapping default case in switches with no explicit default. I'm not sure whether that's valuable or not.
Understanding what effect these annotations have in practice ends up being a small research project every time. Whatever the behavior actually is, @objc communicates our intent less directly than @frozen. I am open to it, but would like some more guidance from the LSG on using these attributes for "off label" purposes.