The thing is that the button always works reliably while all their interface swipes are laggy and become unusable under heavy load, in battery saving mode and as usual, in a few years after they stop optimizing for the old hardware.
I would assume that if they want, they can assign a non-changeable interrupt to the swipe recommendation call.
One could argue that any tactile event would generate an IRQ so it shouldn't matter whether the interrupt handler is from the screen or home button, except that there intuitively seem to be many more branches and CPU cycles required to determine the actual priority/intent of a tactile interrupt versus a smaller set of branches required for the home button.