Oh, I see what you’re saying. Since the compiler synthesizes forwarding members for all projections the wrapper type itself doesn’t need to be public.
This is possible but it would be a bit strange. Without the wrapper being visible outside the module the projections would look like hand written members with strange names. This might also have implications for documentation, etc as the documentation would be provided on the wrapper type. For these reasons I’m not sure allowing wrapper projections to be more visible than the wrapper type would be a good idea.