I would like to make a few comments on this. We've been testing various redis alternatives quite extensively for use as a cache in WP and I recommend staying with redis in enhance or using apcu.
You should note that the real performance bottleneck is the serialization of php data. This is a computationally intensive operation and unless other forms of serialization such as igbinary (which is unfortunately not supported in enhance) are used, it will wipe out the differences between object storage engines.
Dragonfly is faster in benchmarks because of multithreading and more modern memory structures, but it doesn't benefit much with serialized wp data. It is also much more resource intensive. That's why it's ideal to deploy it as a large central server, but where there is some extra network latency.
In enhance, a redis server is included in every container, so you actually get something similar to a multithreaded dragonfly,
because you're running a lot of redis processes.
If you are running multiple different sites on the enhance server, then the configuration by OP is also a serious security threat, because then the object cache is accessible to all sites and their objects (user passwords, for example) can be read and modified.
If you need a better object cache, you need to focus on serialization first. This is also where various wp dropins/plugins differ. I think the paid version of Object cache PRO tries to address this.
However, I recommend giving the good old APCu a chance. It is not used on shared hosts because it is not safe to run it with multiple sites, but in isolated enhance it is ok to use. The advantage is that it eliminates the need for serialization and network communication, the disadvantage may be the deletion of the cache when restarting the php process.
Of course, I recommend that you do your own tests. A gigantic woo eshop that has a whole server to itself can really benefit from dragonfly with the right serialization.
