FileVault 2 encryption doesn't have much of a performance impact, either during the encryption process and/or after the encryption had been completed. Going from FileVault to FileVault 2 certainly did have performance and/or functionality improvements; however, most of the actual performance increase came from the Intel/AMD CPU. Since about 2010, the Intel/AMD CPUs include the AES-NI instruction sets, that's basically offloads the the encryption overhead from the CPU to the AES-NI. In another word, it's hardware based encryption in the CPU, that brings me to my question...
Does macOS FileVault 2 support Self Encrypted Drives, or SEDs? These type of drives are very common nowadays, be that HDD, SSD and NVMe PCIe x4 card, pretty much all of them support Opal SED standards. Instead of encrypting with FileVault 2 the already encrypted content of the SED drive, FileVault 2 could just manage access to the encryption keys that reside on the Self Encrypted Drive.
In the Windows world, Bitlocker is Self Encrypting Drive aware starting in Windows 8 and newer versions. Upon activating, Bitlocker will not encrypt the drive's content and instead, controls access to the SED's encryption keys. Moving the drive to another system and/or booting the PC to a removable storage media still requires authentication for the Self Encrypting Drive. In this case, it pretty much acts the same way as setting the hard drive password in the BIOS/EUFI in the PC world.
Maybe FileVault 3 will have this functionality for future Apple desktops and laptops? If I recall correctly, Apple currently does not ship any system with SEDs that comply with the Opal standard. Maybe I am wrong, or at least I hope I am...