I have not heard of any specific conflicts between these two. In general, if running multiple security plugins, to avoid most conflicts, it is best to avoid enabling features in both plugins that do the same thing.
For example, blocking brute force attempts with both plugins at the same time may cause one plugin to report the attempts, and the other one not to reach its limit. I have heard in the past of a different plugin that would tell the user how many attempts they have left, but users would get locked out earlier by the settings that the user chose in Wordfence.
Some other features may work just as well when both are enabled, but just be aware that when either plugin is updated, it may introduce new conflicts. If you have a test environment for sites where you will use this combination, I recommend testing updates there before applying them on the live site(s).
Most of the article that you mentioned may not apply in this case, since it goes in depth about cloud-based firewalls that act as a proxy for your site, where they may not protect against attacks that determine your server’s real IP. (In those cases, you have to change your DNS records to point to the cloud service.) It’s up to you if you want to try running both, and see if there are any benefits — if you do have any problems where a feature in either plugin isn’t working, just remember to try turning off the other one temporarily to see if it is a conflict between the two.
-Matt R
