I considered what you wrote before posting initially, but unfortunately our logic is flawed.
Silicondust makes tuners. They can be used with many different pieces of software. Because of this, the Silicondust tuner must [by default] do the one job that it was meant to do, present the software with every tuning opportunity available, and then let the software (and ultimately the end user) decide what to do about it. Doing anything otherwise would be compromising the one and only job the tuner should be doing. This is by design at Silicondust, so I don't see them changing it, or any need for them to, unless they are interested in adding a variable that could potentially introduce confusion with numerous other pieces of software.
Furthermore, when a developer undertakes the project of designing and selling a DVR software, whose primary function is to record television, and a user indicates that the final result is a missed recording, I would think that would garner some attention, especially when it is 100% within the developers ability to fix the problem their customer has brought forward.
I would consider a workaround by selecting a different tuner where the developers may have opted to include the option, but, well, you know ...