[Solved] Guitar Rig 5 channel switching embedded into the track??

Hi all,
 
    I have an old audio track and at some point I had purchased Guitar Rig 5 and was playing this track to find a close sound to then modify. I just reopened this file and tweaked emulation to something I prefer and saved it. The issue I have is that near the end of this track, the switching of GR5 presets that I had done long ago was actually saved, and is embedded in this track "somewhere." I checked events list, disabled read/write parameters, even copied the audio to another track (and as soon as I load GR5 as an effect I get this switching back!!). To my knowledge I had never armed this track when playing it back long ago, yet GR5 has automations (I assume) someplace that are switching cabinets near the end of the track. How do I find and delete these (and what "are" they really)?
 
   As an aside... I "believe" this is also the project I had issues  before where GR5 would suddenly "not work." I deiniftely need to understand better where these "automations" are being recorded, since I see this becoming a nuissance in the future.
 
   Thanks all in advance!
   Michael

OMG... I never even considered this, and have many tracks in this file. How would I go about finding such a thing?
 
As an aside... since my last post was also on GR5, I submitted both to NI directly and linked these forum posts in the help ticket. I am baffled as to where (and more importantly WHY) this data was saved. I do not believe I ever armed this track, but had recorded another track that has since been deleted (so if embedded there, would it not go away also, or is it "global" somehow?)

I went and played with this some more. One interesting note is that one of the cabinet setups this track switches too did not even exist until last weekend! I have not saved the file, so that was just "odd."
 
Basically, I deleted the effects, copied the track to a new project, reinserted GR5 and the issue is back. I disabled both track read automation, as well as globally, and it continues to do this, so I am now incredibly baffled as to what exactly this is. The events list is blank, and disabling read automations doesn't stop it (I also disabled all the plug-in parameters from SONAR).
 
NI sent me a response to try to first clear the controller, which I did, but to no effect. They also suggested that the triggering data is in the track itself, which is a pretty solid assumption after copying this to a new project.
 
I will have to play with this some more to see if I can resolve it. I am going to redo this particular track anyway, but am more concerned for the "what if" event that I do this on something "final." One work around is that other plug-ins are not triggered by these, even GR 4 (go figure). It would also help to know how I inserted these mysterious automations in the first place, so that I do not do it again (this particular track was first recorded 13 years ago).
 
Yikes.... Another massive concern with this I just verified :( If a project is NOT bundled... the audio track "master" is modified, since it is really only one file that is pointed to by SONAR. I just opened an X1d version of that file and inserted GR5 on that same audio track... and the automation issue is identical... so it is embedded into that audio track. Definitely a point for bundled backups!

Update: I created a new track from scratch with X2 and seeing the same issue with GR5. It is a different pattern but repeatable. Does anyone know how to shut off read automations in GR5 itself? Doing it as a plug-in seems like an X2 overlay, so is not actually affecting GR5.