What's interesting is - I saw this issue when I was doing initial testing for upgrading to WC 13.0 from WC 12.0 before I joined PTC. It seemed to be an issue until I went to testing the production environment, where the issue went away. We had a 3 tier environment (DEV, Staging, Prod). DEV and Staging both saw symptoms of this where startup time was much longer than the previous comparable environment (Dev 12 to Dev 13, STG 12 to STG 13). Staging was set up to mirror what our production system would look like including resources. And it still started slowly. On the production VM, we didn't see the issue... and strangely enough, by the time we got to testing upgrades with what would be the prod WC 13 machines, the issues were fixed.
One thing to maybe look at is what does your security software do? We used a heuristic scanning tool (Sentinel One) and by the time we got to production, we had exceptions built in to address issues found in testing. Tools like Sentinel One inject themselves in EVERY java process unless excepted. We had many anomalies with this, that caused all sorts of performance issues
