We do not want functions that take floating point arguments, only u32 should be used. And don't get me started on more than one argument!
you cannot convert an function that calls async code into a sync function.
u32 / float does not have the problem. It does not "bubble up", unless you want it to.
You can only convert an int to a float with significant caveats. It's not a general trivial conversion. More complicated types may not be convertible at all or behave in all sorts of exciting ways (including having arbitrary side effects).
The point is that none of that is different to async functions. Of course you have to know what to do with them for them to be useful, but there is no requirement for them to "infect" calling code.