No, the issue you're thinking of is at BIOS+MBR partitioned systems cannot make use of larger disks than 2.2T due to 32-bit LBA addressing issues. This is not an inherent limitation; the article you point at literally describes how to use GPT instead.
You've essentially said "my Windows box is limited to 640KB", I responded with "no it isn't", and you've replied with "well this old way of doing things is limited" while pointing to a DOS command prompt on your Windows box.

So there's a little bit of truth in there somewhere, but it isn't actually a relevant limit, because the thing we're discussing is whether or not the hardware is capable of running TrueNAS.
The SAS 6/iR typically included with Dell workstations of that era is NOT able to address more than 2.2TB. This is an etched-in-silicon limit, and is relevant to TrueNAS.
The Windows "limit" you mention is only meaningful for Windows when installed using BIOS+MBR. However, since you could boot from a 2TB BIOS+MBR disk, and then add a 10TB GPT-partitioned disk to the system for your data, this isn't even a hard limit for Windows -- just for its boot disk, and even then, only if your system doesn't support GPT. You need to plug that second drive into a controller that doesn't have an etched-in-silicon limit, of course. Whether or not this Window is broken is not particularly relevant to the poster's question, in any case.
The relevant limit is the etched-in-silicon 1068 controller 32-bit LBA restriction. The only way to avoid that is to use something else, whether that be AHCI SATA, PERC H200/H310, etc.