Thank you for the question and suggestion. Unfortunately, using the name likely creates other aliasing security issues, since it can be reused across auth-methods in different scopes and could also be pointed from one auth-method to another within the same scope.
With that said, this “chicken and egg” dilemma with oidc is a known problem. We’re still pondering solutions on our end that could make the workflow better for TF.