Despite the fact I typically hear V13 very well it is not a station I follow much, a few times a year I make sure I have the current schedule and make a recording just to confirm the format is still the same. So I was not monitoring the morning of the 19 April when you saw the issue. However since you posted I have been recording the 1200 and 1300 time slots, just to see what is happening.
How sure are you that the carrier on 7501.5 is CNR1? I ask for several reasons, but foremost is that I cannot hear much audio on the 7501.5 kHz signal so I myself can’t tell what it is, I know only that something is there, however it does not really appear typical of CNR1 operation.
What I am seeing at my location is that there is definitely a station on 7501.5 kHz, in AM mode. However, it is very weak by comparison to the V13 on 7502 kHz, V13 being S8 or more in these time slots, often up to 20 over S9. 7501.5 kHz is so weak in fact that I cannot really tell the language and CNR1 is typically strong on most of the other freqs I can find it on, for example in the same time period the CNR1 on 7445 kHz is S9 or better. Yes, I can tell there is something on 7501.5 kHz, but it is very weak here in southern California, and not really affecting reception of V13, for me, at all.
The carrier on 7501.5 kHz is present when V13 is not on the air. For example, right now, 1415 UTC and more than 45 minutes since the end of the last possible V13 transmission, the 7501.5 kHz station is still present.
Also, CNR1 does not typically shift off frequency of the station it is jamming. It is atypical for CNR1 to jam a station on 7502 kHz with CNR1 service 500 Hz off on 7501.5 kHz. Normally CNR1 sets right on the same freq and hammers whatever its target station is.
T!