Well I guess the '32' gives away that it isn't official Google Chrome in that case but a fork which still provides 32-bit versions.
I think the old-school UA string has always said 'x64' in recent times, 360Chrome was/is the same.
The discrepancy doesn't seem to be causing any problems with Cloudflare-protected sites as yet, at least none of the ones which I use.
It's not pretending to be a higher version of Chromium now at least, which it used to with earlier versions.
Does Cloudflare even look at the old legacy UA string now?