Whenever the user may naively be using the last value of a higher-frequency probe, there should be a warning. There are already some warnings/errors along these lines, but I think there are some cases that still get through. It would be good to enumerate the potential issue cases here, including those already handled.
One challenge is that the frequency of a report column is always subhourly. So extra code is needed to check against the user-input frequency of the User-Defined-Table (UDT).