The gamepad API provides raw input, and Construct implements the deadzone itself based on the raw input. But if you want something more advanced than Construct does, you can already get the raw input in gamepad expressions, and implement your own (possibly dynamic) deadzone.
Alright good to know, never thought of doing it that way. I always thought this was some sort of JS thing, that needed to be declared before "initializing" the gamepad.