There is absolutely no way to ‘fix’ this without deactivating the plugin or totally rewriting it’s behavior.
The problem is the code isn’t ‘wrong’ but it’s been written in a way to prevent it from ever being overwritten. Now it’s important to note that your content is not actually deleted or edited, it’s just filtered. Unlike most of our hacked code, this is crazy obvious what it does. If it had been base64’d and hidden, you’d know it’s bad. But as it looks right now, this isn’t bad code, is it? Well, the problem with the code is that there’s no way to turn off the filter without editing the file directly, as explained in the original the original Stack Exchange thread.