Gragorg

The requirement for an array device is going to be removed in a future release.  The ZFS zpool has higher performance but drives do not spin down.  The array allows you mix and match hard drive sizes and expand one drive at a time when needed.  It also spins down unused drives to save power but performance is limited to the performance of a single drive as data is not striped.  If you lose one drive your data is covered in both cases (array and raidz).  If you lose two drives the raidz pool you would lose your data while the array would only lose the two failed disks and all remaining data would be intact.  You can add a second parity to the array to have a two disk fault tolerance. 

Possibly the router updated and restarted?  If you type //broxi into the web browser it should load your gui regardless of ip.

You shouldn't have to change swags container ports from 80 and 443.  Container ports are unique to the containers.  Domain forwarding in router is not required that is what SWAG does.  On your DDNS docker did you remove the email field?  If this allows Cloudflare DDNS to run you don't need DuckDNS to track your ip that is what Cloudflare DDNS does. Your containers don't really need any configuration since SWAG is just directing to their exsisting web gui.  Having said that I was a former SWAG user and found it to be not very user friendly to add new proxy entry.  I now prefer Nginx Proxy Manager as it is very simplified.  Also why did you have to change port 80 and 443 for unraid?  If your only looking to use only Nginx in Swag then NPM is far more simplified.  These are the videos that I used to accomplish reverse proxy using NPM if you want to go that route.
 
Buy Domain and connect it to cloudflare. Here is a great video
Follow DynDNS portion of this video at 9:20 skip the duckdns part.
I used this video for NPM

If your Extended Smart test is good and you want to clear the status you can hit the "Clear Stats" button at the bottom of the main tab.  If the counts increases it will show back up.

Hit the little "?" icon in the top right corner of the gui

Keep appdata and domains on the Cache.  it is so much faster and lower power consumption.  My Mx500 I use for my cache shows Power on hours as 6y 3m 14d.  I wouldn't really worry about SSD wear and tear.  If your worried about it you can mirror 2 in a cache pool.  Shares such as media and what not are stored on the array.

Follow this video from Spaceinvader one.

Under the Scan Automatically tick on plex it says
 
"Your library will be updated automatically when changes to library folders are detected."
 
Mine does not stay spun up.  If your have the plex appdata on the array it will keep the disk(s) it is located on spun up.

It acutally pretty easy to do.  Here is a great video by Spaceinvader One which covers what your trying to do.

Spaceinvader has a great video on this here.

Your CPU wasn't the bottleneck for parity rebuilds.   170 MB/s is about all you will get with any CPU