So I modified the script a bit after installing the new power adapter to test.
Now using windows command 'choice' for 1 second delay (about 1.03 secs).
choice /N /C A /D A /T 1
Still takes 2-3 seconds after issuing a tune to frequency or release tuner command for the numbers to stabilize.
Reason for cablecard cc: bps=38810720 is tuner0 was recording when I ran this on tuner2.
tuner2 Frq:117MHz at 17:39:36.42 (hdhomerun_config FFFFFFFF set /tuner2/channel auto:117000000)
delay a second at 17:39:36.49
get debug info at 17:39:37.52 (hdhomerun_config FFFFFFFF get /tuner2/debug)
1 second after tune.
tun: ch=auto:117000000 lock=qam256:117000000 ss=98 snq=100 seq=0 dbg=-441/3823
dev: bps=0 resync=0 overflow=0
cc: bps=38810720 resync=1 overflow=0
ts: bps=0 te=0 crc=0
net: pps=0 err=0 stop=0
delay a second at 17:39:37.58
get debug info at 17:39:38.61 (hdhomerun_config FFFFFFFF get /tuner2/debug)
2 seconds after tune.
tun: ch=auto:117000000 lock=qam256:117000000 ss=98 snq=100 seq=100 dbg=-441/3803
dev: bps=38810720 resync=0 overflow=0
cc: bps=70000672 resync=1 overflow=0
ts: bps=38810720 te=0 crc=0
net: pps=0 err=0 stop=0
delay a second at 17:39:38.67
get debug info at 17:39:39.70 (hdhomerun_config FFFFFFFF get /tuner2/debug)
3 seconds after tune.
tun: ch=auto:117000000 lock=qam256:117000000 ss=98 snq=100 seq=100 dbg=-441/3823
dev: bps=38810720 resync=0 overflow=0
cc: bps=77621440 resync=1 overflow=0
ts: bps=38810720 te=0 crc=0
net: pps=0 err=0 stop=0
release tuner2 at 17:39:39.76 (hdhomerun_config FFFFFFFF set /tuner2/channel none)
delay a second at 17:39:39.82
get debug info at 17:39:40.85 (hdhomerun_config FFFFFFFF get /tuner2/debug)
1 second after release.
tun: ch=none lock=none ss=0 snq=0 seq=0 dbg=0
dev: bps=0 resync=0 overflow=0
cc: bps=43367840 resync=1 overflow=0
ts: bps=0 te=0 crc=0
net: pps=0 err=0 stop=0
delay a second at 17:39:40.92
get debug info at 17:39:41.95 (hdhomerun_config FFFFFFFF get /tuner2/debug)
2 seconds after release.
tun: ch=none lock=none ss=0 snq=0 seq=0 dbg=0
dev: bps=0 resync=0 overflow=0
cc: bps=38810720 resync=1 overflow=0
ts: bps=0 te=0 crc=0
net: pps=0 err=0 stop=0
delay a second at 17:39:42.01
get debug info at 17:39:43.04 (hdhomerun_config FFFFFFFF get /tuner2/debug)
3 seconds after release.
tun: ch=none lock=none ss=0 snq=0 seq=0 dbg=0
dev: bps=0 resync=0 overflow=0
cc: bps=38810720 resync=1 overflow=0
ts: bps=0 te=0 crc=0
net: pps=0 err=0 stop=0
Since I'm not having issues and none of my normal 30+ minute recordings show any errors, just consider this informative.
But, it would be interesting to hear from others with HDHR's what their numbers look like.
Here's the windows command script I'm using in case anyone wants to try it
testdebug.cmd
REM
REM testdebug.cmd Windows command script to tune an HDHR Prime tuner2 to a specific frequency and check debug status at 1 second intervals
REM
REM output is redirected to file 'testdebug.txt' in current directory
REM replace all hdhomerun_config 'FFFFFFFF' with the 'Device Id' of a specific HDHR, otherwise it runs the commands on all HDHR's
REM replace all 'tuner2' with 'tuner#' desired, 3 tuner Prime has tuner0, tuner1 and tuner2
REM replace all '117' with frequency in MHz desired
REM if hdhomerun_config not in path, use full path "C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config"
REM
REM tune HDHR Prime tuner2 to frequency 117MHz
REM
echo tuner2 Frq:117MHz at %TIME% (hdhomerun_config FFFFFFFF set /tuner2/channel auto:117000000) >testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF set /tuner2/channel auto:117000000
REM
REM use choice to delay for one second
REM
echo delay a second at %TIME% >>testdebug.txt
choice /N /C A /D A /T 1 >NUL
REM
REM get debug status from HDHR tuner2 at 1 second after tuning
REM
echo get debug info at %TIME% (hdhomerun_config FFFFFFFF get /tuner2/debug) >>testdebug.txt
echo. >>testdebug.txt
echo 1 second after tune. >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF get /tuner2/debug >>testdebug.txt
REM
REM use choice to delay for one second
REM
echo delay a second at %TIME% >>testdebug.txt
choice /N /C A /D A /T 1 >NUL
REM
REM get debug status from HDHR tuner2 at 2 seconds after tuning
REM
echo get debug info at %TIME% (hdhomerun_config FFFFFFFF get /tuner2/debug) >>testdebug.txt
echo. >>testdebug.txt
echo 2 seconds after tune. >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF get /tuner2/debug >>testdebug.txt
REM
REM use choice to delay for one second
REM
echo delay a second at %TIME% >>testdebug.txt
choice /N /C A /D A /T 1 >NUL
REM
REM get debug status from HDHR tuner2 at 3 seconds after tuning
REM
echo get debug info at %TIME% (hdhomerun_config FFFFFFFF get /tuner2/debug) >>testdebug.txt
echo. >>testdebug.txt
echo 3 seconds after tune. >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF get /tuner2/debug >>testdebug.txt
REM
REM release HDHR tuner2
REM
echo release tuner2 at %TIME% (hdhomerun_config FFFFFFFF set /tuner2/channel none) >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF set /tuner2/channel none
REM
REM use choice to delay for one second
REM
echo delay a second at %TIME% >>testdebug.txt
choice /N /C A /D A /T 1 >NUL
REM
REM get debug status from HDHR tuner2 at 1 second after releasing
REM
echo get debug info at %TIME% (hdhomerun_config FFFFFFFF get /tuner2/debug) >>testdebug.txt
echo. >>testdebug.txt
echo 1 second after release. >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF get /tuner2/debug >>testdebug.txt
REM
REM use choice to delay for one second
REM
echo delay a second at %TIME% >>testdebug.txt
choice /N /C A /D A /T 1 >NUL
REM
REM get debug status from HDHR tuner2 at 2 seconds after releasing
REM
echo get debug info at %TIME% (hdhomerun_config FFFFFFFF get /tuner2/debug) >>testdebug.txt
echo. >>testdebug.txt
echo 2 seconds after release. >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF get /tuner2/debug >>testdebug.txt
REM
REM use choice to delay for one second
REM
echo delay a second at %TIME% >>testdebug.txt
choice /N /C A /D A /T 1 >NUL
REM
REM get debug status from HDHR tuner2 at 3 seconds after releasing
REM
echo get debug info at %TIME% (hdhomerun_config FFFFFFFF get /tuner2/debug) >>testdebug.txt
echo. >>testdebug.txt
echo 3 seconds after release. >>testdebug.txt
"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config" FFFFFFFF get /tuner2/debug >>testdebug.txt
EXIT
UPDATE: have to include this in this older post as the forum won't allow me a new post here. That's OK as I feel I'm just talking to myself anyway 
More data points;
Wondering how this is possible with DVR tuner sharing, unless Channels DVR actually is issuing a new tune command to the HDHR when it says sharing connection.
Issue appears with the 5th, 6th and 7th 1hr recording from the same channel starting at 16:00
[SNR] Statistics snq=99%,0%-100% seq=99%,0%-100%
All recordings are good and processed by my video editor with no errors.
2020/07/26 12:00:00.014427 [DVR] Starting job 1595790000-335 The Untouchables on ch=[376]
2020/07/26 12:00:00.457706 [TNR] Opened connection to 1323AADB/0 for ch376 KQCADT2
2020/07/26 12:00:00.458052 [DVR] Recording for job 1595790000-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1200.mpg" for 1h0m29.98542234s
2020/07/26 13:00:30.459120 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1200.mpg": ss=97%-98% snq=100% seq=100% bps=2960267,582048-6873280 pps=293,62-660
2020/07/26 13:00:00.017964 [DVR] Starting job 1595793600-335 The Untouchables on ch=[376]
2020/07/26 13:00:00.018260 [TNR] Sharing existing connection to 1323AADB/0 for ch376 KQCADT2 (clients=2, len=0)
2020/07/26 13:00:00.018504 [DVR] Recording for job 1595793600-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1300.mpg" for 1h0m29.981876419s
2020/07/26 14:00:30.006427 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1300.mpg": ss=97%,96%-98% snq=100% seq=100% bps=3065047,582048-7637312 pps=302,62-732
2020/07/26 14:00:00.014164 [DVR] Starting job 1595797200-335 The Untouchables on ch=[376]
2020/07/26 14:00:00.014430 [TNR] Sharing existing connection to 1323AADB/0 for ch376 KQCADT2 (clients=2, len=0)
2020/07/26 14:00:00.014671 [DVR] Recording for job 1595797200-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1400.mpg" for 1h0m29.985687033s
2020/07/26 15:00:30.012330 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1400.mpg": ss=96%-98% snq=100% seq=100% bps=3158224,582048-7641824 pps=311,62-733
2020/07/26 15:00:00.013791 [DVR] Starting job 1595800800-335 The Untouchables on ch=[376]
2020/07/26 15:00:00.014035 [TNR] Sharing existing connection to 1323AADB/0 for ch376 KQCADT2 (clients=2, len=0)
2020/07/26 15:00:00.014254 [DVR] Recording for job 1595800800-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1500.mpg" for 1h0m29.986065995s
2020/07/26 16:00:30.023695 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1500.mpg": ss=96%,95%-98% snq=100% seq=100% bps=3197519,582048-7641824 pps=315,62-733
2020/07/26 16:00:00.013923 [DVR] Starting job 1595804400-335 The Untouchables on ch=[376]
2020/07/26 16:00:00.014174 [TNR] Sharing existing connection to 1323AADB/0 for ch376 KQCADT2 (clients=2, len=0)
2020/07/26 16:00:00.014380 [DVR] Recording for job 1595804400-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1600.mpg" for 1h0m29.985927145s
2020/07/26 17:00:30.053924 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1600.mpg": ss=96%,95%-98% snq=99%,0%-100% seq=99%,0%-100% bps=3277283,0-7694464 pps=322,0-738
2020/07/26 17:00:00.058708 [DVR] Starting job 1595808000-335 The Untouchables on ch=[376]
2020/07/26 17:00:00.058945 [TNR] Sharing existing connection to 1323AADB/0 for ch376 KQCADT2 (clients=2, len=0)
2020/07/26 17:00:00.059163 [DVR] Recording for job 1595808000-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1700.mpg" for 1h0m29.941151946s
2020/07/26 18:00:30.017942 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1700.mpg": ss=96%,95%-98% snq=99%,0%-100% seq=99%,0%-100% bps=3373916,0-8655520 pps=332,0-830
2020/07/26 18:00:00.013309 [DVR] Starting job 1595811600-335 The Untouchables on ch=[376]
2020/07/26 18:00:00.013552 [TNR] Sharing existing connection to 1323AADB/0 for ch376 KQCADT2 (clients=2, len=1316)
2020/07/26 18:00:00.013764 [DVR] Recording for job 1595811600-335 from 1323AADB ch376 into "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1800.mpg" for 1h0m29.986543852s
2020/07/26 19:00:30.038905 [SNR] Statistics for "TV/The Untouchables/The Untouchables 1959-10-15 2020-07-26-1800.mpg": ss=96%,95%-98% snq=99%,0%-100% seq=99%,0%-100% bps=3323166,0-8655520 pps=327,0-830
@eric
I think if you started sampling at 3 seconds, or threw away that first result from your first inquiry at 2 seconds I wouldn't be seeing this.
Still curious what your HDHR Prime results look like.
I've been recording eight 1hr back-back overlapping recordings from the same Prime channel for the past 3 weeks and see issues in the log that don't reflect reality. Not a big deal, UNLESS you rely on that log data. Still the same on v2020.08.12.1854 today.
The HDHR logs show the tuner was selected and not released for eight hours.
Every back-back overlapping recording shows that it was sharing the existing HDHR tuner connection, yet every one shows seq=99%,0%-100% bps=#######,0-####### pps=###,0-###
I know this is a result of your first 2 second sampling. If the code can't be fixed, than everyone should know that this is NOT an issue with their tuner, but your code. Led me to buy a new power adapter for my HDHR, which wasn't the issue.