Okay, this is very weird. I got a replacement drive for the one that had SMART errors (which I have also told not to store unduplicated data on until I trust it). I put it in and tried playing around with the balancers again. Even though I would now have almost 4 TB free, enabling "Disk Space Equalizer" still wanted to put unduplicated data on drives where the higher priority balancer "File Placement Limiter" had been told NOT to put unduplicated data on the drive. As per the screenshot, and as continues to be, there is a red tick mark below the graph showing how much space is being used on the drive that when highlighted correctly shows "Unduplicated file placement limit 0.0%". Per Drashna, I unchecked in Disk Space Equalizer, the Balance using unduplicated files option and it had no effect. However, I reversed them. I left checked, equalize using unduplicated, and unchecked equalize using duplicated. THIS changed the behavior, however that seems reversed to me. A check saying to balance using duplicated should only use duplicated files, but the exact opposite is happening. It now is balancing placing no unduplicated files on the drives I requested, exactly like I want it tom, and showing that it will be trying to fill all drives to the exact same percent used. I haven't checked, but maybe there is a new version of this balancer? Mine is 1.0.1.
Alex, everything above is behaving like I expect it to with the exception of the above described behavior in Disk Space Equalizer. I had changed File Placement Limiter to allow 99% of the drive to be used. It didn't put unduplicated data on my drive N:\, but it also didn't balance it, the unduplicated data was just moved to other drives. What I expect to happen is because I have File Placement Limiter as the highest priority, that other balancers shouldn't overwrite a setting telling it not to store any unduplicated data on "x" drive. To me, that should be a rule that is followed unless there is no space for duplication (clearly not the case in my system).