Thanks everyone. Maybe I'm expecting too much. If you're using a custom URL why wouldn't you want the rest of your child pages to inherit that same custom aspect?
A good example would be when your navigation structure doesn't mimic exactly your content tree. Take my "services" example. I simply want a folder named "Services" so I can point my main navigation structure to that directory but I want all the URLs to not have the /services node in them. Thus I use the custom URL. Another example is I place all my "landing pages" in a folder called landing pages and I change the custom url to remove the "landing pages" node because it's not needed and the client doesn't want it. Now if my landing page has a form on it and the client want's a "thank you" page, I need to modify that thank you page as well. When I link to any one of my custom URL pages, it shows the URL correctly.
If I wanted to have it as an alias and redirect I'd do that but that's not what I want. Seems like there should be some sort of inherit property in this area.