First of all, let me reassure you that we take any reports about CPU usage seriously, since we want VEPro to be as efficient as possible.
A busy GUI code, updating meters, peak displays, MIDI activity and other things, will always use some CPU power. The cost for updating such things tend to be a bit higher on MacOS than on Windows, due to blitting being a more expensive operation on MacOS. I don't find the CPU usage of VEPro as such to be in any way abnormal for the amount of work that is done.
In order to shed some further light on this topic, I created a performance comparison project, trying to isolate the impact of GUI updates on project performance. The results from this test, and the 16 possible test permutations, can be found in the linked PDF.
If anyone wishes to look further into the measurement data, or reproduce these findings - I am also enclosing the project files
Test Results (PDF)
Raw data and project files (ZIP)
Thanks,
Martin