I don't see a reason to have debounce on form input widgets. The main reason for the debounce is to keep the stress on the backend as low as possible. You could also delay client actions that could be resource intensive. So that means that we await further action until the user has stopped typing (fixed amount of time) and then perform the action that the input would trigger. I use this normally on a filter input for a table. When filling in form you normally don't have queries to the backend but if you do, only apply the debounce on the inputs that are triggering backend actions.

I hope this helps,

Vincent