I did a test of it enabled and disabled and it didn't really make much of a difference. I do currently have it enabled though.
The Build Larger Shares feature helps best with algorithms that have higher mining volume, so it may not have as large of an effect if your rig is not mining those algorithms frequently. Some users have also reported increased earnings on Blazepool by disabling some algorithms, such as hmq1725, skein, tribus and c11, that frequently have big fluctuations in both price and mining volume. Alternatively, you can define price adjustments to create a switching priority for certain algorithms over others. For example, I have one user who prefers to mine Lyra2v2 and Raven, so he added a price adjustment of 10% for just those two algorithms on the pools he mines. The software will still switch to other algorithms, but only if their prices are significantly higher than his preferences.
You've mentioned before that you prefer to keep the miner settings on the defaults, but a few of the users on my Discord channel have also increased their earnings by following Z-enemy's intensity and difficulty setting recommendations for all the algorithms that that miner supports.
I'm not really interested in keeping a lot of alt-coins laying or spending time exchanging them manually. I have a small portfolio of coins that I HODL and Ravencoin is one of them. I was using HiveOS (Linux-based) before, nothing against your software, I would probably go back to that to avoid any extra developer fees. Hashrate in Linux was also a little better than Windows using Nevermore.
As I've mentioned before, I appreciate the fact that you tried the software and have given me the opportunity to respond to your concerns. I encourage users to try other products to see which solution works the best for their specific rig and mining strategy. If you feel that HiveOS or something else works better for you, I can respect that. Aside from keeping the mining software up-to-date and providing users with the ability to easily tune a wide variety of performance parameters on per algorithm/card basis, there is only so much I can do as a Windows developer to work around the constraints of the operating system and device drivers.
This approach would spread my rig out too thin. I find that if I'm not using the entire rig to mine on one pool only, then my profits really take a dive and it takes too much time to get paid out.
I was just mentioning it as a possibility. My point was only that the software does not have to be used for auto-exchange. Some users don't mind a slower payout if it means higher earnings over time. Others prefer fast, steady payouts. I try to support both types, but different strategies require some trial and error to dial-in the optimal settings.