FabricPool, inactive data reporting and deswizzling

Hello to the community,

according to this KB, deswizzling affect inactive data reporting.
We usually do vol move to balance capacity/performance across our aggregates, and when the move complete, a deswizzler process starts on the volume.
Deswizzling could run for an undeterminate period, this KB suggest to disable snapshot to let it complete (who wants to do it on a production volume?...)

My question are:

- Can deswizzling become a problem for FabricPool behavior?
- Can we rely on wafl.deswizzle.afs.first option to speedup deswizzle process? (that caused inconsistency issues with Ontap 8, a real nightmare)
- Do vol move will be optimized to eliminate the need to deswizzle data in future Ontap releases? 😉

Thanks 

Lorenzo