I can only say it should fix it for this particular old WebGL 2 bug. The problem with issues like this where there are vague reports of problems across a scatter of different devices, is it's hard to know whether it's all the same problem or a range of different problems, and if there are multiple problems, then how many devices are affected by any one particular problem. Without a full diagnosis for each device, I can't say how much this will help. I guess we will make the release, you can update your app, and then we'll find out.
The screenshots of the phone only really deepen the mystery: the "WebView" app version 3.3.5 looks like an unofficial app, and is possibly unrelated. The "Android System WebView" app is the official one, but no version appears to be noted. The best way to check is to display the browser user agent string somewhere in the app (since you can also have multiple webview apps installed this way will clearly identify which one is in use). Note the full text of the "Software update needed" message also includes the user agent string, which is important diagnostic information to pass along if you can (it identifies the specific WebView reason and the exact features it's missing that prevent it running the app). Perhaps some Android manufacturers ship their own unofficial WebView app? I've never heard of that before, so I doubt it, but lots of manufacturers do awful things to their devices. The Android System Webview is an official component of Android and updates independently of Chrome.