We use SCCM extensively at my office, and yes, it's entirely possible to tell it to reimage every single computer. You just need to target the deployment at "All Systems" and make it mandatory. My guess is that some admin picked the wrong collection, which is fairly easy to do in SCCM 2007 (2012 has Collection folders, which helps with that), and there's no warning messages -- just a summary of "this deployment is going to these devices, click Finish to do it." Of course, most other mass management tools assume that the admins know what they're doing, so they don't have much in the way of guard rails either.
One of the more obnoxious elements of SCCM is that there's no real way to recall a command you send out; clients pick up policy at periodic intervals, and without manual intervention, they'll just grab the policy and do what it says even if you kill the server in question. You can block deployments by taking down distribution points (if the clients can't grab content, they won't run the deployment), but you still have to be fairly quick about it to stop it.
What we do to prevent these sorts of disasters is implement process around the use of the ConfigMgr console and ensure only the people who know how to use it actually use it. To prevent an OS reimaging incident, our OS deployments go through a static set of collections by process and are always optional (requiring a manual touch, either at PXE boot or in the UI) except for a specific set of collections that are segregated in their own folder and have names and descriptions with scary words that make it clear what's going to happen. For instance, in our "Clean Reimage" folder, we have a collection that says, "Windows 7 Reimage (Clean, PXE, Forced)" with a description to the effect of, "*** A computer placed in this collection will be REIMAGED and LOSE ALL LOCAL DATA. Local state is NOT preserved or transferred. ***" If we were a larger IT organization, we'd probably use SCCM's role-based security to limit access to clean reimages to a specific group of people.
If you actually bother to read the Federal Register text, you can see in the second paragraph of the introduction that the JOBS Act, and this subsequent regulatory structure, only applies to crowdfunding where the reward is a security. It specifically explains that this is different from the current model of crowdfunding in the U.S., where the donors receive some "token of value" related to the project, not a share of future financial returns. The SEC isn't trying to regulate the current system, but is trying (as directed by that law) to allow crowdfunding where the donor award is a security; the current regulatory structure, based on the Securities Act, largely makes this sort of model impossible due to the various requirements of public offerings.
So, there's nothing to get up in arms about. This is just a move by the SEC to allow something that isn't currently permissible under U.S. law, not an attempt to "tax Kickstarter" or "regulate Indiegogo" or whatever other nonsense people claim.
You have programmers. You have multiple projects. They might be working offline. For this, you really need a Distributed Source Control system such as git or mercurial. I personally recommend mercurial as it's got good Windows tools (TortoiseHg and HgScc for Visual Studio integration). You can put your "pure" repository on your share, then have the programmers push to it -- or, better yet, have an "incoming" for each project to which anyone can push, then a "pure" to which only project leads have write access and into which they can push approved versions.
If, for some reason, you simply can't run source control, Windows offers Offline Files functionality that can sync individual folders if you set them up correctly. What this means is that you need to ditch this "shared drive" concept and set up your file shares correctly -- by which I mean having multiple shares, one for each project. Users then connect to the share in question and choose to make it offline, or you create drive maps and enforce offline files using group policy.
Actually, as the people who found the first RT jailbreak noticed, the only thing keeping Windows RT from running ARM compiled applications (which you can create in Visual Studio, even!) is a policy that mandates that only Microsoft-signed executables can run outside of the WinRT environment. If Microsoft removed that restriction by changing a single registry key, all of that compatibility would suddenly appear. In fact,
Yes. Turn off Secure Boot in the UEFI firmware menu (accessed through Advanced Startup), then boot off the USB Linux boot device of your choice. I expect a modern distribution of Linux will have drivers for most of the hardware inside the Pro. Alternatively, run it in Hyper-V (or VMware, or VirtualBox, or the hypervisor of your choice), since it's an x86 Windows 8 device with hardware virtualization support.
Only the RT has the "permanently locked" Secure Boot setting. The Pro is a full-fledged i5 device that can run Linux just fine.