You are on the correct track, however working on the wrong device I feel... As mentioned those seem to be the separated list I fond in that early OS, and are the switches between the Corvette and Standard OS versions. Would allow you to disable or enable the current list of broadcasted ID's. But this is can also be accomplished by switching to a Corvette OS release, which flips those switches for ya. But year related Issue is we need to Add to that existing list if we want to run against newer TCM OS versions.. Or we tell the TCM to not require our E38 missing ID's. Easier.. But you have the proper approach going on.
For those of us who play nicely with others and don't plagiarize, might have a complete Global A dbc, and thus the ability to regenerate all these networked messages on the bench. While knowing exactly what each bit is for and does. Then ya take recorded CAN data from XXXX year / model vehicle, hack it up to build a short msg file, then we play that back against our target ECM, TCM, BCM of choice. If ya do it right, the node will tell you happy or not per msg back over CANbus, and actually give you the exact reason if it isn't under some other ID's. If ya have the matching A2l, one can take said response and go digging for that exact line where it's unhappy. Easy...
So that's our basic approach required to matching up nodes across 25 years. GM didn't delete much, they just added to the stack. Replicating the missing data is easy, modifying existing data packets requires a different approach.
