No - Part of how interrupts work is that the CPU itself pushes the values of certain registers onto the stack (As well as an error code in the case of an exception). The CPU has to store those values somewhere so that when the interrupt is finished it can return to where the CPU was running when the interrupt happened, and the stack is the obvious location to do so. You can't tell the CPU to do anything different in this case, so you're forced to simply make sure your stack pointer always points to the top of the stack so it doesn't get clobbered.
At the end of the day, it's not really that big of a deal - Allowing the redzone only really allows you to avoid two `sub` and `add` instructions on the stack-pointer. It's a nice idea, but losing it isn't that big of a deal at the end of the day. The majority of functions can't take advantage of the red-zone anyway, because any function that calls another function has to make sure its stack-pointer is correct before calling it.
At the end of the day, it's not really that big of a deal - Allowing the redzone only really allows you to avoid two `sub` and `add` instructions on the stack-pointer. It's a nice idea, but losing it isn't that big of a deal at the end of the day. The majority of functions can't take advantage of the red-zone anyway, because any function that calls another function has to make sure its stack-pointer is correct before calling it.