That's not correct. If you send any other CC besides CC69 along with the PC message, it does process everything correctly.
Although this can be done, this would be just a non elegant workaround for this faulty behaviour. The Hx Stomp offers snapshots for a reason. This is the same reason I would not like to replicate similar presets, occupying 2 or 3 times more presets than I should.
Just adding an additional info: I have registered a support ticket. However, the answer I first got was that "if the CC command is being sent via instant commands, along with a preset change, then the preset change will supersede the snapshot change. Since the preset does require the process to load it onto the HX Stomp, the CC command can't be done at the same time", and "Its much easier to simply save the preset desired to with the snapshot you want. Then change it after the preset has been loaded".
Honestly, I got really disapointed with this answer, because technically this is not correct, and I had someone from Line6 telling me that it would be "much easier" to have an approach where I could not take benefit of the snapshots. Well... I reiterated the question, based on two main arguments:
A.) Before version 3.0 was launched, it did work (based on customers reports)
B.) When I send any other CC command, along with a preset change, the preset change DOES NOT supersede the CC command. I tried sending preset change along with CC49, CC50, CC51, CC71-0, etc., and all of them work, but not CC69.
The answer I got was: "I will need to look into this further, and see if our team has seen the same thing. We are currently getting alot of requests, so it may take me some time to attempt at reproducing", which is, again, very frustrating... :-(