I'm making a reply to my own post in case anyone comes looking for an answer.
So there is an inherent problem with my methodology here. The parameter feature at a channel level still triggers a event, so dynamically writing to a channel parameter triggers an infinite loop that the FlexLogger cancels in the background.
Long story short - don't do this.
The goal of this plugin was to send string data representing system state as well as waveform data. I will make a separate post about sending strings to FlexLogger if you are looking for something similar.