Clarification on Change History feature

This is regarding a clarity on the recently released feature - Change History (https://docs.couchbase.com/server/current/learn/data/change-history.html)

To my understanding, this feature will preserve all the data changes in a document without de-duplication. whether this feature will be having impact on all the DCP consumers. In other words whether all the DCP consumers will get all the changes happened on a document, especially the eventing.

Context: one of the customer needs to perform an audit tracking on all the changes happened to document. As there is no in-built feature for the same, they are planning to use the eventing to achieve the same. However there is a possibility that some of the changes may get missed out due to the deduplication logic which is present in the DCP streaming. So more clarity is required here to understand whether enabling this feature will solve this problem and if not what the road map for the same.