Yeah, I’m rooting for @ruro’s idea also because it looks the most likely to be accepted despite it being a solution to only a specific (but again, the biggest) use case of multiple metaclasses.
Would be nice if my other, more general solution gets accepted but the sheer simplicity and elegance of @ruro’s idea makes it more likely to succeed.