Question: should enforce (internally) to -t 0 (i.e., wait till the device replies) on state.* functions?

state.* typically take a long time to execute, and the run time is probably not often known or immediately obvious. In that case, the command is executed with `-t` to ensure salt-sproxy waits for the reply sufficiently. Now, `-t` is either 0 or a very large value. So I'm wondering if it wouldn't make sense to just default it to 0 natively on state.* function, out of the box?