Does the Seagate FireCuda 540 2TB cause too much system bus occupancy when loading dense assets in Ghostwire: Tokyo, and can priority tweaks fix it?

This drive is insanely fast, but it's actually so fast that my CPU scheduler couldn't keep up. Walking through the streets of Tokyo felt like a slideshow. The Seagate FireCuda 540 2TB was pushing I/O queue depths over 128 during high-concurrency reads, which caused the system bus to choke between game data and background updates. I tried the 'turn everything off' approach with background apps, but the frame drops persisted. I had to get aggressive with resource limits. I used an I/O scheduling tool to set the game process to 'High' priority and disabled Windows Search indexing for the game folder. In the performance monitor, the disk response time stopped jumping between 12-35ms and settled into a clean 3-7ms range. I actually overshot the limit at first and saw some textures pop in late, so I had to loosen the queue depth threshold to 64. Temps are sitting at 50-62℃. I exported all the optimized I/O throughput data via the system log tool for my records.