Impersonation Tokens UI is missing read_registry scope

I notice that in the UI where an admin can manage impersonation tokens for a user, the read_registry scope is missing from the selectable scopes. This scope is available for regular access tokens and I was able to add a new token through the API with a read_registry scope, so I assume it is just missing from the UI. Or is read_registry scope not supported for impersonation tokens yet?

If it is just an UI glitch my request is simply to add read_registry to the list of scopes. If it is not yet supported, I suggest that support is added :)