1) It's the added CPU overhead of some stuff in Sailfish, and maybe some lacking power management stuff. It's bearable - definitely not as hot as running NITDroid.
2) Nope, only option's to reflash. The NAND area that displays the image is locked (to programs using the CAL library) from writes.