Thanks for all your comments. Looks like some people like and dislike the article but this is to be expected.
Apparently some are commenting that the article name is misleading. Actually it is not. The purpose of the article is to help get the master database back up and running. Replacing the master database with a working "copy" is the same as rebuilding it. Technically you are replacing the database but the end results are the same. So if you restore it, copy it or rebuild the master database who cares as long as the business can get to their data. Without the business DBAs would be out of work.
Others comment on the fact the this can not be done everyday. Well, you don't have to. It's all up to you how you want the run your environment. My "Real World Example" is how I use this process. It's for our disaster recovery site. I also run this process on our production servers when we do patching on the OS and/or SQL server. Since SQL server services will be interrupted during our maintenance window I execute a batch file that does the complete process in under 5 minutes.
If you can see the benefit of this process and can use it great.
If you don't like the article, maybe you can post your improved process other than reading off the BOL on how to rebuild your master database.
Hopefully you will get inspired and write your our process/tip and post it on this great website.