Don't want to sound too melodramatic, but at present, if AIDA64 is stopped, Aquasuite quite happily continues showing the last recorded temps.
Dunno if AC have plans for this, but at the very least could be a cheap&dirty optional check on the software readings every x seconds. If all the readings are the same after y times then a warning can be given. Not great, better just to test if the appropriate sensor process is running - only 2 are allowed so it should hardly mean much coding.
I also have the Software sensors up and running. Personally, I cannot see any danger in the default behaviour if there is a fault, because I do not see ANY useful function for these data points other than Data Monitoring. The CPU temps for example change from one instant to the next based on workload, and Motherboard temps may be useful for controlling a Chassie fan, but I personally use a temperature sensor on the AQ5 to control an exhauset fan based on case ambient temps. All radiator fans and the pumps should be based on Radiator inlet or outlet temps for control functions.
On the other hand, if a guy might want some action from his LED,s, he mught set up a controller useing a CPU software temp sensor to turn it on and off. However, if the software sensor defaults to 50C, the only thing that happens is the LED stops changing.
AMD FX-8150 OctoCore O.C. 18% to 4.2 GHz on ASUS M5A99X EVO with 16 GB Corsair Dominator W. C. RAM, 2 nVIDIA Geforce 560TI W.C. in SLI, six Western Digital drives for a total of 4.07 TBytes, AquaComputer Aquero 5 Pro, AquaComputer D5 pump, Multiswitch USB, tubemeter and Kyros CPU block. Two coolant loops,CPU & SLI, MB, RAM and AQ5, with two flow meters. Running Windows 7 Professional 64, and using Open Hardware Monitor v0.5.1Beta Aquasuite B16 hardware temps.