@Nyssa - as I have said above there is very little I can do, beyond not using user_none's code for MOBI files. And even if I go down that route, you will still have the problem of when you send the book to your Kindle that the page count from the generated apnx file is going to be the same wildly inaccurate values for those books.
This has all been discussed previously on this thread (start looking at page 2). IIRC user_none was reluctant to change the existing logic because his focus was on performance, he did not want to significantly slow down the sending to device process.
The only resolution I can think of that "might" keep everyone happy, is offering an option in the APNX file generation to pull the value from a custom column, rather than always generating using its (clearly drastically flawed in some cases) current counting implementation. That way this plugin can use whatever approach it wants to (such as pulling from a website, with a fallback to counting based on the max of <div>,<p> or <blockquote> tags). And then when you send the book to your Kindle, this "better" page count value could be used on your Kindle.
How much work that would be to implement if it is agreed and whether user_none has an interest or is willing to have the existing code changed is quote another issue, it would impact his standalone apnx file generator plugin as well.