@cryzed - there is no magic algorithm to give you what you want, as has been said many times in this thread algorithms like APNX can only approximate based on some variables and assumptions around average paragraph lengths, number of lines etc. All of which becomes moot given users can choose different line spacings, font sizes, margins, screen sizes, CSS attributes... There is *no* amount of "twiddling" with these will get you anything more satisfactory across more books (or indeed across an entire book).
The only reliable way to solve this problem would be something in the Kindle firmware to compute the page turns. But presumably that requires a fair amount of computation which would impact the performance and battery life of the device so they don't do it either.