The result was not good - splotchy. Click on the image to see how splotchy it is.
BTW the original image had plenty of noise, especially since I only had 2x5 min SII subs (the other ones were 10x5 min) so I had to crank the heck out of it and reduce the blown up stars before I got the above image. The processed SII image had a ton of noise, which you can see.
Later I rescaled the image to speed things up to 1000x668 and got a much better result albeit at noticeably reduced resolution (but not a whole lot, and it is so much quicker).
Then I went on to 2000x1337, this is the one I like best:
and 3000x2005, here the large-star imprefections begin to show:
Bottom line, the 1000 image processes the large stars best but suffers from reduced resolution. The 2000 image fixes the resolution problem and shows minor artifacts from the large stars. The 3000 image increases the resolution but starts to suffer even more from large star artifacts. The original-size 6249 result is garbage (and takes forever to process).
I also played with the stride parameter. As it turns out, 64 is a good value. But if you are in a hurry, try 128 because the difference could be unnoticeable but it is 4x faster. If you get about at least 400 tiles you should be OK, 1000 is better.
Hopefully this is useful for those complaining about StarNet++. Apparently you can get much better results much faster if you reduce the resolution! StarNet++ is free and can be used without depending on a plugin program such as