Thats interesting. Thanks. I have found over the years that many systems, including my own, show initial promise but have some flaws like you have pointed out. Where the rubber meets the road is if in pointing out a flaw(s), one can contribute and possible fix. The key, imo, would be to focus on the large drawdowns and see what coding rules can be applied to avoid them.
Regrettably, in my early years, I ran into far more people who said 'that won't work' than those with constructive suggestions for improvements.