To confirm, the issue is on 8.0 only. 8.1 and later, including 9 do not exhibit the issue. I am omitting device types simply because I am not in front of the console at this time, but I am confident that it is OS version and not device hardware.
This is what I have done in my environment, but first I am assuming you have set up correctly Android for work/enterprise on an OG, and that you are aware of the difference between Android legacy and Android profiles.
I created an Android profile that is a custom type with the xml. This profile is called by a compliance policy.
Create a compliance policy for Android. Use the the os version policy and if the os version equals 8.1 then call the policy you created above. This will disable the chrome browser in 8.0.
If all these work managed devices enroll in the same OG then create a restrictions policy that meets the conditions you need including clearing the box for ‘allow chrome browser’. This profile is applied to all devices in the OG. You also have the option to control via smart group, or whatever they call those groups.
In my setup I ensure only the 8.0 devices have the custom xml, this was necessary last year when devices from Samsung and blackberry and others released 0s update from 7.0 to 8.0. Not so much an issue.
Anyway, I hope this clarifies what I have done. One final thought, troubleshooting logs should capture when a profile is applied. If the browser is showing up after it is hidden via profile, I would think the profile was either removed or reapplies. The logs should capture that.