ok but heres a silly question (its silly because it should not be necessary to resort to such elaborate methods...)
but if can attach the android adb (from another computer). and then launch the rigol andoid apk app. or vendor.bin whatever it is - instead of launching this binary executable in the normal fashoin. you could kill the running process instance. and prevent it from relaunching automatically...
then launch it manually yourself via the remote android adb debugger. this would then permit to pause and freeze the execution just before / after the touch event tapping the screen. to then use the step-thru and step-over (single step) debugging around that flashing of the screen.
and perhaps modify the settings value thru the android adb debugger.
but there could be much simpler and easier ways to modify the relevant setting directly. for example on the filesystem, or in the flash etc.
but another route is either file a bug report, asking rigol for a beta build with such fix in it. or alternatively do other things (which again, should be totally unnecessary or silly / too much work)
this is assuming that the observed behaviour is definately a bug in those firmware builds... or maybe it's actually a different type of bug. whereby your scope's own settings area has gotten corrupted. then the firmware is trying (correctly) to load or save those relevant settings page. but the action fails since that block or specific file of settings is in fact corrupt. which then is working fine on everybody else's scopes. (but that is just purely a speculation - i have no idea).