I'm not in your area, of course, and not familiar with the systems you are programming.
However, looking at your file, I don't see anything that would cause or explain the issue you are having.
When the file is loaded, & the 325P2 is scanning, are you seeing the quick key indicators on the display?
View attachment 198873
That first item. in this case "S0", indicates that the system quick keys showing are single digit (1 though 0 (zero)
The asterix in the #3 & #9 slots indicate that while a key is assigned, it is currently off. The dash ("-") in the 'zero' slot indicates nothing is assigned for that key.
View attachment 198876
View attachment 198874
This screenshot shows "S7", so the system quick keys are 71, 73, 74, 75, and 70. The dashes indicate no QK assigned. (Sys QK 72 was being scanned when I grabbed this screenshot. The key being scanned blinks on & off. It so happened it was 'blinked off' at the instant I grabbed the screenshot.
When you load a programming file from ProScan to your scanner, the default (in ProScan) is to first delete the existing program in the scanner.
View attachment 198877
If, perhaps by accident, you had unchecked that box, you could possibly have two copies of the same system on the scanner. so that when you turn off, say, 71, it actually turns it on in the duplicate system.
With your scanner monitoring the system, focus on whether the #s. like 70, or 71, actually flip from showing the second digit of the QK #, meaning it is turned on, to an asterix, indicating that while that system number is loaded, it's QK is set as "off". Remember that a "-" (dash) indicates that that particular key number has not been assigned.
Maybe someone else will have a different take or suggestion for you to try, Right now, I'm scratching my head right along with you.