The problem with this is that it loses the opportunity to give us hints about contexts that should be async but aren’t. Doing this would either require an opt-in to always show the warnings, or a separate tool that does all the analysis redundantly.
(See also: Auditing potentially async code)
This, like deprecation warnings, seems like a case where judicious use of optional warnings (and selective -Werror) would be to everyone’s benefit.