After my trusty old Atten/Siglent decided to brick itself, I just got my new DSO2D10 via Amazon AU - a bit cheaper than Aliexpress or Bangood, free shipping from AU to NZ and delivered in a week. Out of the box, it's a pretty good scope for the money, but my motto is "If it's broke, fix it; if it ain't broke, hack it till it's even better".
So first, many thanks to the contributors to this forum for their excellent hints and advice, and to DavidAlfa in particular for his expertise and the various hacks and tweaks on google drive.
My DSO2D10 came with the latest firmware installed, but I reinstalled it anyway, along with the DSO2000 and Keysight PC apps and driver, then ran a full platform-tools backup and Backup_Builder for safety's sake.
First I upgraded it to DSO2D15, all OK except that PRIVate:READ:EEPROM still showed DSO2D10. Not sure if this causes any issues, but PRIVate:SET:MODEl1 and PRIVate:SET:MODEl2 to DSO2D15 fixed that issue.
Then I installed and tested Factory_Reset_Daemon (just in case of lockups), and installed the Small_English_Font which made the interface look a lot nicer. I also installed bmp2png_Daemon for when I want to save screenshots, and then used patcher to change the trace color for channel 1 to orange (CH1_COL="\xFF\xA5\x00") instead of yellow, to match the button color.
It would be nice if patcher also changed the ID, Trigger and channel block (at the bottom of the screen) but I can live with that.
Finally, I tested and overclocked to CPU_OC_PLL_N=28, CPU_OC_PLL_K=2, CPU_OC_PLL_M=2 and MEM_OC_PLL_N=16, which appears to be rock solid stable so far.
The only thing I haven't succeeded at so far is installing the USB Console "dso3kb_usb_console_install.upk" - it gives a message "Update Failed! Error code is -3". Not sure why this is, any help appreciated.
Anyway, it's a significant improvement on my old Atten/Siglent and I'm loving it so far - no lockups or odd behaviour (yet!)