I'm getting a few scattered reports of this behaviour so something may have changed in a DNN Version that I wasn't aware of.

If you're of the technical bent, the way it recognises page name changes is through the regex value of 'triggerDictionaryRebuild'.  This regex is applied to the rewritten url, and if a match is found, the page index is rebuilt, which will include the 'new' page urls (the same effect as doing an app restart).

You can experiment around with this regex value and see if you can make it capture the page changes you are talking about, or, if that is out of your skillset, then I will be doing the same thing and posting the results.

No headway just yet.  It's on my list of urgent bugs so I'll be looking at it as soon as I can.  It's been a hectic couple of weeks for support.  I'll post back when I've got something new for you.

To answer your other question - all you need to do is understand the different rewritten urls that each action takes - by action I mean 'action that impacts the urls'.  You can see what the rewritten urls look like by turning friendly urls off completely and going back to the default.aspx?tabid=11 style.  When you change page settings, or add a new page, look at the urls and see if you can find commonality in the Url for the postback.  Then simply craft a regex that will match the correct ones and not match every other time.