Shmokes, that's kind of the point. How a computers handle date/time is really well hammered out (at least for non-Windows systems. Noticed one of the recent MS updates last week is/was date/time related. I assumed it was to do with time zones, but now

). For anyone to strike out and kludge their own date handling methodology is just stupid.
In any case. As a consumer, people expect a Sony product to work as expected at all times. Sony
selected the defective component, Sony should have done the testing that would have spotted the defect (which appears to be the case if the slim models aren't affected). Let Sony punish the company that manufactured the defective chip, but that doesn't absolve Sony from responsibility. (Now if the engineer intentionally misled Sony on the quality of that component, then you might have an argument).
Here's a thought. If 2010 is incorrectly labeled as a leap year, would that mean 2012 and 2014 are also mislabeled as well? Are the owners of these ahem.... defective PS3's doom to actually taking a break from game playing every February every second year?
If they could even make the fix? The issue would appear to be a flaw in the chips design itself, so if the chip is going to do bad math one day, it's hard to work around that.
It depends on what, exactly, causes the flaw. It's not the first time a hardware flaw appeared and a software patch was applied as a fix. I remember having to toggle a compile option to work around the Pentium float math error.