Note that _Unwrappable is already present in the standard library for bridging.
However, one principal use case for such a protocol relies on the fact that only Optional conforms to it. This is essentially the case here also: it's meant to be a workaround for not being able to write a parameterized extension. If other types could conform to the protocol, then it wouldn't be a workaround for this issue.