T2DParticleEffect & cloning

I made a template of a T2DParticleEffect to clone and use multiple times. Once I make the clone/copy, I access and use the CurrentEffectData property and the EmitterDataList to control the particle effect dynamically at runtime. This works great if there's only one T2DParticleEffect, but the minute I use clone to make a copy, both particle effects get an internal reference to the same T2DParticleEffectData instance in the CopyTo function and that has the undesired effect of my dynamic manipulation of its data affecting both unique instances of the T2DParticleEffect class at the same time.

Question: Is there a better way I haven't thought of, or am I going to have to create a unique instance of the T2DParticleEffectData class myself, copy over all the variables, and assign it to the CurrentEffectData property after the clone?

It seems like the particle system was not designed for dynamic runtime manipulation due to its shared data, but I really need to have unique instances of the variables that drive the emitters in order to support certain types of dynamically-controlled effects in my game. It would definitely be nice if it was configurable whether to share the data or instance it when cloning.