We've solved the problem of data contention on a disk a long time ago...
Grub may not operating within an OS sandbox, but it is required to play nicely with the OSes it is booting. The way to do that is to wrap your data in a partition or a file.
grub-the-comman-line-utility writes to those sectors but it runs in linux userspace so it's really in the same position as the windows programs that also write to the reserved space...
Think about it, if an application can write to the boot area then you've got a giant hole in your security.
Hell, you can flash motherboards from an OS... writing to the boot area is just one example of many 'giant holes in your security'.
http://www.stoned-bootkit.info/
http://www.h-online.com/security/news/item/Bootkit-bypasses-...
http://www.anti-forensics.com/modify-truecrypt-encryption-bo...
That said, no application without a very high level of trust (perhaps above what an Administrator can do on Windows) should be able to write outside the filesystem. This should, at the very least, pop-up some "Program X is about to do something remarkably stupid. Allow or deny?" dialog.