No, false, the thing is, just because it's open does not mean you can just take it. Because the code they stole, was under gpl, which essentially states that they MUST credit the source, and if they made any changes, they have to make it open source. And guess what? they did neither, they tired claiming sx os was entirely their own.
Yes because a error that modifies memory is WAAAAAY more likely to brick than intentionally placed brick code, that is checked at every point in the bootloader. And writes to the boot partition of the switch, and locks the nand when and if triggered. Which the boot partitions have key blobs related to that system. So when it bricks it, you better pray to god you have a backup. Because getting one from someone else, isn't going to do you any favors.
Wow... hang on let me frame this as a question. If some team decides to steal incomplete code from another developer, and add slight modifications, and then they claim their project is complete, is it actually complete? According to you we shouldn't use tx or Atmosphere. Since if you really think about it, TX is just a incomplete atmosphere with a couple of patches. (And brick code)
On another side note, cfw always has a small chance of bricking a console. But unlike most custom firmware, tx has brick code, and flaws that could accidentally trigger it. And even if a brick happened with atmosphere, it would be far less severe than what tx's brick code. So stop defending it, and do research.