Possible solution is to create custom filter widget. Once the change event of the filter input is triggered the filter method is called. So you can execute the filtration by manually triggering the change event when the user types:
To make mine look/feel like the adjacent built-in filters, I added the same classes to the parent span and used k-input-inner instead of k-textbox. Also, to help convince the browser to stop trying to autofill, I added an autocomplete attribute.