This is less of a comment on the article than a comment on the feedback above.
There are security reasons for intentionally not making settings available remotely. These are the same reasons that ASP.NET blocks all *.config files. If you hosted your settings with a virtual path, your settings would then be exposed when they probably shouldn't be.
If you find that you absolutely must have settings stored remotely and you aren't concerned with the security implications of doing this, then a relatively simple solution might be to implement your own RemoteSettings custom configuration section which would be fairly easy to do.