To do so means we would need to extend similar overload-resolution affordance to throw'ing functions. However, the "if we're in a throwing context, prefer the throwing variants" approach might not work as well because we have try? and try! to suppress errors at an expression level, whereas there is no equivalent for async/await.
In we do extend this affordance for throwing, it would likely also need to be part of a major language version bump because the change in overload-resolution rules would probably change the meaning of or break existing code.
Doug