#618 Performance bug with system volume encryption

[camel]

Hello, in Windows 11, I tried changing the settings for VeraCrypt's "Do not use the following number of logical processors for encryption/decryption" dropdown. When the number of processors selected in the dropdown is maximized, boot time measured from the end of the password & PIM entry to the Windows login screen is relatively fast but after logging into Windows performance seems slow and BC's benchmark test shows relatively low speed. On the other hand, when the number of processors is set to 1, boot time is very slow but after logging into Windows performance seems fast and BC's benchmark test shows fast performance.

In my testing, with only 1 processor selected in the dropdown, boot time was more than twice as long as boot time with the maximum number of available processors selected. However, with only 1 processor selected in the dropdown, VeraCrypt's internal post-boot benchmark testing showed AES encryption MB/second many times faster than post-boot benchmark testing for AES encryption if the maximum number of processors allowed was selected in the dropdown.

I believe that the setting for "Do not use the following number of logical processors" has inverse effects during Windows boot than it's supposed to have.