ACF should change how it shows details about unsafe html, and in the newest version which has already implemented the escaping, it should restore a show details option. Telling the developer only the name of the field it finds problematic is useless. If the plugin has detected what it considers to be a potential problem, it should be able to report actionable info on what it found, i.e. the page, field name, field content, and reason why it considers to content unsafe, and how it will change it. The current instructions for installing a third party plugin to enable logging and then hunt around the logs to see the details of the issue is not reasonable when dozens of sites are potentially affected.

My most recent experience with this today had me googling for sites like this: https://www.wppagebuilders.com/advanced-custom-fields-plugin-alternatives/. As a longtime ACF Pro customer with an unlimited license who otherwise would have no reason to look to switch, I hope WP Engine will fix this.