Just a bug report. Having the overscan debug info on will be recorded to the high score upon your last life.
That's by design - it shows 3 special values in the menu:
A Sample Overrun value after START. F = 15 which means the digital audio routines went 15 bytes past the end of the sample before the routines could turn off sample playback (as samples will loop if you don't stop them). Using that I determined I needed to add 15 bytes of silence after each sample to prevent you from hearing a brief snippet of the next sample.
Last Score shows detected console, 2600 or 7800, which is so it knows how to decipher the 2600's TV-TYPE vs 7800's PAUSE button to pause the game. The PAUSE button is wired to the TV-Type input but it's a momentary button, as opposed to a toggle switch, so must be handled differently in code.
High Score shows ARM timer value that's used to detect if your 2600 is NTSC, PAL, or SECAM so the proper color values will be used.
Set Left Difficulty back to B and you'll see the expected Last and High score values:
My final entry in my To Do list is:
To Do for Release Candidate
set SHOW_DIAGNOSTICS = 0