Run Veracrypt my self and never had any issue, So there is no general issue with veracrypt
Often when startup takes time it is because MC is waiting for a call to Windows to timeout. Because sometimes windows does not know yet if device that is a network shares is available or not, So the first time it access it it going to take a while before it times out and Windows then caches that.
I never seen an issue with veracrypt. MC see that as any other normal drive.
In Core settings enable full application logging, restart, And then when it start up you can in the log (Ctrl+L) or view the logfile. see what part is taking time.
You can also create a Dump file of Multicommander.exe when it has hanged from TaskManager and then zip that and upload it to
https://multicommander.com/support/uploadThen I might be able to see what it is waiting for.