You can end up with seemingly good reads, despite the facts that they are not for real, especially for systems with weak EDCs, such as pretty much any system that is not based on a generic FM or MFM controller.
Remember, the reads are not constrained by hardware artefacts of PLL, etc that normally affect data read through controllers.
What you get is what you can get, a very slightly different track alignment due to seeking can help though.
You already have a read as far as it gets as a bad read is already stored in the sector image.
You could increase the number of retries as well.
Techniques related to fixing bad reads when read on target platforms are due to different capabilities of the target hardware and won't work once you go to the lowest level.
Instead, you already get better chances than the target would ever have, due to lack of processing capabilities, analysis etc. - FDCs are contrained by the need of real-time usage and other factors.
Although you can simulate similar "fixing" effects in software easily, there is no real reason to artificially create a fake a good/bad read... when you have proof that it's not good at all. It would be more like a comfort zone thing: you got used to thinking it worked, and would give the same feeling despite technically being incorrect.
What one should do instead is a complex analysis of the cells, highlighting weak spots and based on cell behaviour coming up with alternate data pathes. This could be further enhanced with various techniques, but I am not here to give advice for data recovery companies - they already have a very lucrative business