ZFS dedup on a Proxmox host in 2026 — has fast dedup changed the recommendation?

Hi, The standing advice for years has been to leave dedup=off on ZFS pools under Proxmox: the DDT lives in RAM, the write path suffers, and you can't turn it back off for data already written. OpenZFS 2.3 ships fast dedup, which is supposed to address most of that — quota'd DDT, pruning, dedup logs. Has that changed anything on the Proxmox side? Concretely, for a pool that holds both guest disks…