Thanks for the feedback rbabcock!
We will take a look at these. They all look pretty low impact so they would not typically hit our criteria for being included in a patch, but we will see what can be done and when.
Somewhat higher impact - I was just trying to do a scan so I could schedule a server to patch over the weekend. The scan hung up after saying XML was up-to-date and before resolving machines to scan. (Even did this scanning the scan machine.) I saw timeout errors in st.servicehost.netframework.log which were not otherwise reported. I checked the timeout and it was set to 30; changing to 3600 didn't help. (I think the upgrade to 9.2 reset this.) What did seem to fix it was using your operations/database maintenance tool to rebuild sql indexes. (sqlserver 2012 express on the same server 2008 r2 as the scanner.) Scans are now working and no more timeout errors are being logged. They might even be running faster.
A complicating factor: we just imaged the scan server with windows backup and restored onto larger disks. That shouldn't have broken anything, but the initial attempt upgrading to 9.2 ran out of disk space and choked sql server That might have left some damage that wasn't immediately apparent.