Judging by your posts and your handle, you work in or around servers - a lot.
You would probably be aware that security, stability, and all such things are a set of tradeoffs of risks and benefits/costs.
You can make a system 100% secure, but it may not be useable. You can make a system five 9's stable, but you have to pay for it. You make the assessment of the risk (in this case data corruption), against the benefit/costs (double the speed in some cases).
SuSE seemed to have made the assessment of risk without understanding the cost. They enabled barriers by default to take the high moral ground, but then didn't understand the cost of doing so.
Your analogy about buying a new gas oven is interesting. You look at the manuals and there are *many* ways that you can blow up your oven. It is just that the risk (of someone naively or accidentally blowing themselves up) has been balanced against the benefit of lower consumption of energy. There are many ways of managing risks - redundancy, accepting the risk, etc.
My prime point was that the benchmarking which yeilded questions - without the answers given - are extremely valuable. They allow the upstream people developing systems to understand that they need to consider the bigger picture and apply a risk/cost/benefit judgement and not close of all risks. I would expect that in later versions of SuSE they have turned off barriers now that the risk has been sufficiently understood and the costs determined as being commercially relevant.
Or using your analogy. The tests that the oven may blow up but save 50% on the energy bill has been shown that the net benefit is on the side of the oven that may potentially blow up!