If we were to do this, I think we'd probably just make _ProtocolMeta public in typing.py (rename it as ProtocolMeta, and possibly add a _ProtocolMeta = ProtocolMeta alias for backwards compatibility, since there are people who access it in the wild even thought it's private).

However, I'm afraid I would strongly oppose making _ProtocolMeta public. Whether it's exposed in typing.py or types.py doesn't really matter here. As soon as it is exposed publicly, it will become extremely difficult to refactor the metaclass: as with any other class that is publicly exposed and documented, even very small behaviour changes to the class could have the potential to break somebody's working code. Keeping the class private gives us far more flexibility to change the internal implementation details of Protocol without being bound by backwards-compatibility constraints.

As an example: through a series of PRs, I managed to achieve a 20x speedup for isinstance() checks against runtime-checkable protocols in Python 3.12. I don't think this would have been possible if _ProtocolMeta had been public: the Python 3.12 implementation of _ProtocolMeta looks very different to the Python 3.11 implementation. Backwards compatibility requirements would have made such a thorough refactoring impossible.

For your use case, I would consider doing something like this instead:

import abc
from typing import TYPE_CHECKING, Protocol

if TYPE_CHECKING:
    _ProtocolMeta = abc.ABCMeta
else:
    _ProtocolMeta = type(Protocol)

Please be aware, though, that you're using a private class at your own risk, and there are no backwards compatibility guarantees for you if you're doing something like this :)