Sure the situation might exist, but it's exactly the kind of bad engineering I'm calling out.

I guess is the same as on iPhone where if you hold backspace, it will not zap all the text, but go one by one with a visible delay. These companies simply treat end users as babies.

I can't tell the specific concept you're talking about though. If it's the auto-repeat rate (your iPhone example), then of course there needs to be a delay before that kicks in, and a steady repeat rate. I'm talking about single button presses.

If you're talking about the requirement to debounce buttons, the proper way to do this is to act on the button press immediately, while setting a timer that disallows further button state changes while waiting for the contacts to settle. This time is a balance between how long it actually takes the contacts to settle, and how rapidly a user could possibly push a button (missing a deliberate button press is also extremely frustrating and dangerously demanding of user attention, even with tactile feedback).

For sure you don’t act on a button press imediately. If you do that in automotive, all the electric noise will trigger the button randomly.