They should be as responsive as possible. Folks should remember that responsiveness is not what actually defines whether something feels incredibly fast and precise or slow and heavy.
Remember that there is already human delay in the input chain. You are already pressing buttons some number of frames later than whatever your brain saw or heard that caused you to press that button. You do not ever need to account for this delay in-engine.
Now, if you want to try and have your game feel heavier, slower, more realistic, you can do this by adjusting what the response to the button input is. It's software, you can make it do whatever you want. You don't need to insert an artificial gap between receiving an input and doing something with it, it will only create unwanted dissonance in the input chain.
Okay... that's slightly better than what he originally said, but it's still a 6 frame variance gap in a 30 FPS game, when the floor is already such an absurdly high result. So it's still a butt ugly range of like ~333ms to ~532ms. Those are just plain insane numbers.
