Yes, that has been discussed, e.g.
https://github.com/python/cpython/issues/86268
PEP 677 would have provided an alternative syntax for Callable, but the PEP was rejected.
In case anyone cares, my opinion on the matter is:
- builtins.any and typing.Any are too semantically different to share a symbol (you can subclass Any in 3.11!)
- builtins.callable and typing.Callable are at least vaguely the same concept, so it's worth thinking about. For now I'm kind of -0 on it (and reserve the right to change my mind)... the status quo isn't terrible, callable is still somewhat different from Callable (unlike PEP 585 builtins), the import is not the worst thing about Callable, it may have a runtime cost, many IDEs have decent support for auto-importing, things may change (e.g. it would definitely have been a mistake if I'd made the change^^ and then PEP 677 had gotten accepted), etc
I wouldn't say it's a long term goal to cover all typing use cases without imports. In cases where static typing being bolted on to a 30 year old language causes a lot of usability pain, we should aspire to improve things. But dedicated syntax and changes to builtins are about the most far-reaching changes you can make to Python, so some circumspection is wise, potential costs are relatively high, potential benefits in this case are at most medium.