IIRC the conclusion last time around was: these are incorrect readings. The app is responding, but Google's services are incorrectly measuring it as not responding. I think it stems from the new splash screen implementation (used by either Cordova or Android, not something specific to Construct) which incorrectly counts the splash screen as the app not responding. Google need to fix the problem in order to make sure the app is counted as responding when the splash is showing and then produce the correct measurements. So for the time being the fact you see a high ANR does not actually mean lots of uses are seeing your app hang.
FWIW I still think this is weird because even if the splash screen counts as ANR, then the splash screen ought to disappear as soon as Construct shows its loader - which should only take a second or two and not trigger ANR, unless perhaps the device is extremely slow. I'd also advise to make sure the loader style is not "none", because if it is then the splash screen is shown for the full duration the app is loading - if it is any other setting, then the splash screen is hidden as soon as the core Construct engine has loaded and it is able to show its own loader.