Try the other options, btrfs restore is the most likely to work with disk1, if none of the options work can't help anymore, you can try the mailing list or IRC.
If you want future proof look for a Supermicro chassis with a SAS3 expander, those are databolt enable, chassis is also much better than the Norco you were looking at, but also much more expensive.
Or the JMB controller doesn't like that specific disk model, if it was only that disk you can try connecting it to another controller instead, like the onboard SATA ports.
You have an unassigned disk spamming the log with ATA errors, since it's unassigned disconnect it (or replace cables to see if it helps):
ST10000VN0004_ZA2B8RZL
As for the unmountable disks:
Parity can't help with filesystem corruption, btrfs was detecting data corruption, this is usually a hardware problem like bad RAM, if you think that's fixed there are some recovery options here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
Also see here for what to do about the stats errors:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
If you set it to that you'll get a not enough space error for any transfer, that's the minimum free space for disk in that share, when that threshold is met it starts writing to another disk, and there are no 200TB disks.
That's not normal and should never happen, new config by itself doesn't touch the drives, encrypted or not, but without the diagnostics can't really say what it could be.
I was responding to this:
But if you don't have cache you still need to selected the correct setting, or will still get not enough space errors once disks start filling up, depending on allocation method.
That sounds like a Krusader issue, but I never used it.
Disk1 look fine, though short test is usually not useful, unless there are already pending sectors, you should run an extended test when needed, but this looks like a connection problem, replace both cables on disk1.