VSM Replication Failback - Not incremental

I've been told there is a fix pending on this issue. But I've been waiting 8 months so my hopes are starting to fade.

A summary for those that don't want to read: "Failback to Primary" will replicate the whole datastore instead of incremental changes, even with the "Keep snapshot failback" option enabled. This is a huge issue for large datastores and DR testing.

Details: 

I'm using VSM 3.5.2 to replicate my VMWare datastores from Site A to Site B. I have the "Keep snapshot failback" option checked for all of my replication jobs.  

Execute a "Failover from Smart Copy Replica" on a replicated datastore at Site B, the datastore comes online and the VMs register correctly. (YAY)

To failback the changes from Site B to Site A, I select "failback to primary" on the datastore. However, instead of the incremental changes being sent from Site B to Site A the whole datastore will be replicated.

This makes running a DR scenario test over a weekend impossible for me. It also makes any short-term failover impossible due to the fact that the full datastores need to be replicated back.

***If you do this same procedure through GroupManager (manually) the datastore will failback with incremental changes. 

If i'm missing something here let me know. I opened a ticket last December on this issue. The fix didn't make it into the 3.5.2 release and i'm told they can't guarantee it'll make it to the next release either.