We only ever (optionally) delete from Y file-by-file if the same files are not on X (or, vice versa) - for inherent safety reasons. That is to say, we optionally replicate 'absence' created by some external process, but we don't create it ourselves. What the workaround does is leverage the deliberate absence of files in the dummy (empty) location to force this.
We tend to think it's best to leave it that way, so it's less likely to be selected by mistake (you have to really mean it and design it to achieve it). Plus, it's more inherently configurable that way as an fully-fledged independent process (for example, you can use different filters than the main profile does). It's unlikely to be added as 'ancillary behavior' in a single profile, sorry.
We tend to think it's best to leave it that way, so it's less likely to be selected by mistake (you have to really mean it and design it to achieve it). Plus, it's more inherently configurable that way as an fully-fledged independent process (for example, you can use different filters than the main profile does). It's unlikely to be added as 'ancillary behavior' in a single profile, sorry.