As it was pointed out, you had asked a business question in a technical forum ;)
So business angle first. It is all about insurance and risk management, thus somebody from outside is not going to be able to help you a lot. There are IT departments that keep reliability data for their own environments. But theirs is not your environment... You likely have your different hardware with different temperature inside your cabinets, have a different air flow and different power quality from your UPS. Results from somebody else can tell you whether RAID-Z2 is better than RAID-Z1, but you already know that it is...
Unless you are working with a NASA or NSA budget, your bosses are not going to have a risk management study

, they are likely just looking for a technical confirmation of their business decision. One of the simpler technical outlooks, I can think of, is to consider the worst scenario out of the likely ones. Very often it would be a human error that wipes out your primary server. Assuming write speed of your ZFS pool to be 150MiB/s and 23.65Tib (=26TB) of data to be transferred, you get 46 hours for the task. RAID-Z level seemingly was not important, but the disk and network speed were. During those two days, you have only one copy of the data, so RAID-Z level does play a role... Better disks offer better insurance too... (see the thread mentioned in the post just before mine). Of course you should reverse the situation and realize that the same recommendations apply to your primary server.
If you have your systems, perform testing with your data, hardware and patterns of usage. And see what your sustained speeds are for the worst case scenarios (you can think of). For example, try users writing and reading while resilvering. Do these tests both for RAID-Z2 and RAID-Z3 with a varying number of disks. Try to have a non-trivial disk space usage (that is at least 1TiB) in your pool.
Have fun!