It's cheaper, the shielding is lighter, gives about the same results, and the press doesn't hate it so much.
However, it doesn't much matter which you'd use, you'd get superior results. Provided things didn't break in the bounce. That was a particularly nasty prang. The yellow flags are out for sure. I wonder if Murray Walker had predicted it would go smoothly.
The way I would have done it would be to have a radioisotope battery that could run the computers and heaters (if any) but not the instruments or radio. Those should be on a separate power system, running off the battery, although I see no reason why the computer couldn't have an idle mode which consumed minimal power specifically to top off the battery.
The reason? The instruments take a lot of power over a relatively short timeframe. Same with the transmitter. That's a very different characteristic from the computers, which probably have a very flat profile. No significant change in power at different times. The computers can also be digesting data between science runs.
Well, that's one reason. The other is you don't want single points of failure. If one power system barfs, say due to a kilometre-long vault and crunch, the other has to be sufficiently useful to get work done. The problem is weight constraints. It's hard to build gas jets that can steer a fridge-freezer through space, but much harder if there's a kitchen sink bolted on. That means less-than-ideal for both power sources, which means if both function properly, you want to match power draw profiles to power deliverable. That reduces sensitivity to demand, which means you can remove a lot of protection needed for mismatched systems.
What we really need is a collaboration with ESA and NASA to produce an "educational game" where you design a probe and lander (ignoring the initial rocket stage) by plugging components into a frame, then dropping the lander on a comet or asteroid with typical (ie: high) component failure rates. Then instead of abstract discussions, we can get an approximation to "build it and see", which is the correct way to engineer.