Storage Spaces Direct journal disks are, in fact, working as a read-and-write cache for your entire storage pool. When caching for HDD, both reads and writes are cached to provide SSD-like latency (often ~10x better) for both. The read cache stores recently and frequently read data for fast access and minimizing random HDD traffic. That means those journal disks have to be full when operating normally.
In your case, I would rather check the total incoming pool writes (using Perfmon) since your journal size seems to be relatively small compared to the entire pool capacity. Your virtualized production may generate more workload (writes) than your cache can handle, resulting in a significant performance drop due to parallel de-staging of cached data down to HDDs. Try shutting down a couple of performance-hungry virtual machines (if possible) to see if that changes anything.
If the above is the case, your best option to increase storage pool performance would be to replace the SSDs with bigger ones, replace SSDs with NVMe drives of the same size, or add PCIe NVMe disks to the pool for additional caching.
Alternatively, you may replace Storage Spaces Direct with Virtual SAN software https://www.starwindsoftware.com/storage-spaces-direct that uses different storage pool mechanics and true OpenCAS caching (not journaling), offering a much better performance for virtual machines compared to classic S2D.