Hi.
GTech wrote:I apply Ozone on individual modules (Audio Tracks)
You've got me wrong about modules. I'm also using O7 and here's what I meant: at you vst list (inside Mixcraft) you can choose Ozone 7 that opens the full window of Ozone with its modules inside OR you can open any of that modules as separate vst: Ozone EQ, Ozone Dynamics, Ozone Maximizer etc. In my case while full Ozone works well on master, it seems to work much better as separate modules when applied to individual tracks.
GTech wrote:At this point, my CPU/System usage in Mixcraft is under 15%. Do you think CPU usage continues to be the issue? How much do I really need?
Now, I would say no to the CPU as the reason. Looks like your computer is stronger than mine (10 y.o. dual-core) apart of RAM (8 against 16) and I'm able to run full Ozone on master, about 10 Ozone modules, 2-6 iZo Neutrons, 2-6 iZo Nectars plus some heavy delays combined on single tracks with no problems at all. With your 15% it can't be that. (Anybody knows if the RAM shortage can cause the issue?)
What you can do now, is to download the demo of Neutron (has similiar modules and options as Ozone, presets for rap vocals also, and is made to use on single tracks) and Nectar (dedicated for vocals). This will give you some clues: if they also don't work properly, it might be your system's fault. If they work fine, you know it has to do with Ozone only. And who knows, maybe you'll find them as a good enough replacement.
Also try the Ozone as VST2 and VST3. To me there's no difference, some says that vst3 works better.
You can also make a little video with your phone or screen capture and upload it to YT or something. Show your project running, show the tracks settings, master, open the Ozone while track is playing... There's a chance that some experienced user will notice what is being set wrong.