RAIDZ2 in any configuration will yield a total of (drives - 2) x (size of drives) - there's no "wasted space" that is lost based on drive count. You will "lose space" based on converting TB (what your drive is sold as) to TiB (what your bytes are allocated as). Multiply your unformatted space by 0.909 to get an approximation of that.
So 6x3TB = (6-2)x3 = 12TB unformatted, or ~10.9TiB formatted.
There actually can be a waste of space if you use ashift=12 (which most people with modern consumer disks should be using).
See this with detail:
https://web.archive.org/web/2014040...s.org/ritk/zfs-4k-aligned-space-overhead.html
For example, with 12x4TB RAIDZ2 there is a waste of 2.91TiB due to alignment padding and allocation overhead.
Though I should also note that there are ways to deal with this. For example, if you change the recordsize on your datasets (from the default 128KiB) to 1 MiB and you make sure to have compression enabled. Then you can avoid pretty much all of this alignment padding and allocation overhead.
But if you stick with 128 KiB blocks and ashift=12 then you will always have some amount of wasted space unless you are using 6-disks or 18 disks in your RAIDZ2. with 6 and 18 disks the alignment padding and allocation overhead are zero and the only overhead comes from the reserved space for metadata which will always, alawys be there.
I should also note that adding another disk to your vdev will always increase your space. You never lose space by adding a disk, but for some number of disks in your vdev you don't gain as much by adding 1 more disk as you do with other numbers of disks in your vdev.