If the CONFIG_HZ is only used as a fallback, why the big problem changing it? Setting the timer to 250 is a default for servers anyway - desktop systems should be set to 1000 (as per the kernel help files). The remote uses the /dev/input system and as I understand it (I admit my understanding is limited) the polling of the IR receiver is directly tied into this kernel parameter. Setting the timer to 250 means a 1 in 4 chance of the keypress being detected.
If the CONFIG_HZ is only used as a fallback, why the big problem changing it? Setting the timer to 250 is a default for servers anyway - desktop systems should be set to 1000 (as per the kernel help files). The remote uses the /dev/input system and as I understand it (I admit my understanding is limited) the polling of the IR receiver is directly tied into this kernel parameter. Setting the timer to 250 means a 1 in 4 chance of the keypress being detected.