I've never really understood why, outside of multiple OS installs, why you would make so many partitions on the OS drive. You're hurting performance more than helping it, because files on the C partition will need to be constantly accessed as well as the page file on the D partition and then add in the files on the E partition as soon as you start using apps and data. That's a lot of head travel on the drive as it accesses the partition table to find out where to go for each directory track or MFT. On an SSD, probably makes no measureable difference, but on a spinny disk, especially the slower types typically used in laptops - forget it.
Same thin in situations where you want to keep thing separate, like a database server. If they are separate disks, then it makes perfect sense to put the S on one, data on another, and logs on a third. But when it's all one disk or array, putting multiple partitions on a single physical disk is WORSE.
The only thing I'll say about FAT32 vs NTFS is that since the earliest versions of NTFS, I have NEVER had a drive that, as long as it powered up and could be seen by the hardware (so- - no blown board, or failed platter motor or head stepper, etc), I have NEVER had one I couldn't recover data off of using NTFS. Corrupted and not bootable - pull the drive, put it in another machine, do a disk repair, put it back in the original machine and now it boots. Transactional file system FTW, cleanup undoes any incomplete transactions and returns the state to what it was before the corruption occurred.