Hmm, porting from WAMP testing to LAMP deployment is not quite that easy for everyone - some packages are specifically Linux-only, usually due to issues in the way they've chosen to manage the file system.
If you choose to run a server from home, check with your ISP who will probably say that's not permitted by their ToS. I'm not sure I understand you correctly but if you're using DH for your PC backups you may find DH frowns on that too.
As to getting your feet wet with your own server, I think part of the fun is getting to know the environment, and you've got an "impedance mismatch" by practicing on Windows and deploying in Linux. If you plan to test on Windows and deploy at a different shared/dedicated host that supports Windows, be aware of all of the software that your system uses, especially DLLs or other packages that need to be installed via an MSI file. You can easily install this on your home system but a shared or even dedicated host won't be as generous. When using your own system you have more packages open to you, you can run services as persistent processes, and you have more freedom to write to the local file system.
The things that prevents me from running a full-blown system from my home office are 1) ISP ToS, 2) ISP reliability, and 3) Security. Point 1 was mentioned. Point 2 means I don't want my business to suffer when the guy next door is getting a new ESPN channel and the workman outside has to take down my service for a few minutes. More realistically, I'm not setup here to support an outward facing server if the power goes out - that's why we pay for hosted services. The biggie is #3. You don't know what you don't know, and if you're going to host a public server you need to do your homework to ensure you aren't exposing an obvious attack surface - obvious to people who spend their time on such things, not obvious to those of us who use web servers simply as tools to deliver content. Again, this is one of the things for which we pay our shared host.
Setting up a server and getting apps running is deceptively easy. It's that next step at keeping them properly maintained that's going to start eating your time, and perhaps money, if you're not prepared for it. I recommend spending time with books on Windows security for websites, just to get an idea of what that world is about, and also in forums where other people are doing the same thing you want to do - like this forum, community support is the fuel that keeps the internet burning bright.
Also, don't rule out installing a free vmWare Server or similar offering, and hosting Linux there. You can get pre-configured systems that are plug n play and you can copy the environment for learning/development/testing. I have no preference between Linux and Windows and I don't like the related religion - I host with Linux and do all of my development over Windows with .NET - use what you're comfortable with.
I prolly have more to say to a direct question, but for now, that's nuff outta me.