If you want to improve the quality of your software the best thing you can do is actually to use a tool whose purpose is exactly that. So, sit down and reread your code, or sit down and use a static analyzer on it. But porting it to other systems is not the right tool for the job. It might find you a bug or two by side-effect. But if you want to find bugs then your time is much better invested in a tool that checks your code more comprehensively and actually looks for problems rather than just a small set of incompatibilities with your software.
Porting is in fact a quite bad tool for this job, since it shows you primarily issues that are of little ineterest to the platform you actually are interested in. Also, due to the need for abstraction it complicates reading the code and the glue code increases the chance of bugs, since it is more code to maintain.
So, yupp. If you want to review your code, then go and review your code. If you want to staticly analyze your code, then do so. However, by porting you probably find fewer new issues than it might introduce.