Tien, adding more RAM to one CPU and leaving other will lesser wont work, as it's not just the RAM, you have to consider CPU L1/L2/L3 cache's as well, as RAM can be increased and decreased, what will you do with cache's?
Keep memory mode to Normal, as others (Mirroring and Sparing) are for mission critical circumstances, Memory mirroring is as same as creating RAID 1 on storage, and in Sparing mode, one stick will be left spare until other memory module fails and spare will take over (memory level redundancy). but NUMA Enabled and Disabled is something that can work, so naturally you will set NUMA to be Disabled.
When I mentioned interleave, every server manufacturer has different BIOS options, where Fujitsu has enable/disable option, it should work.
As you'll be adding RAM, make sure all modules match and they are in correct banks, as I have seen buffoons from Dell sending servers with memory installed in wrong banks. there must be two colored banks, start populating the ones closest to CPU (e.g. if black one is nearest to CPU, then populate all black ones on either sides, unless every bank is populated in your machine. secondly all modules MUST match in terms of speed and latency.
Lastly, you mentioned having additional slots on server, are you referring to SATA connections or PCI slots? though SATA SSD's will work, but if you can add additional NVMe RAID card just for Database and rather than choosing SATA, get NVMe drives and keep database on that. The E5 platform unfortunately is not capable of booting through NVMe protocol drives, else I would have recommended NVMe boot drive and database, as SATA has latency of 30-100 microseconds while NVMe has just a few microseconds, and in database application latency does play its role.
Just to keep you informed, why I recommended moodledata on HDD's (so in case you have to justify your institute or have knowledge of what and why you're doing), when cron runs and your courses are backed up, it's moodledata folder that gets temporary copies made of the backups before saving it at your desired location, so for example if your courses are for 100GB, it will be writing 100GB of data on drive before creating backup file, and doing it everyday means by month end you'll have written approximately 3000GB (3TB approx) data already, SSD drives have a downside of number of writes, a standard SSD has life of 200TBW (Terabytes Written), datacentre SSD's (which you'll be getting) have much higher TBW's, but in the end they have life, so I recommended moodledata folder on HDD's so your drives can last longer. BUT do remember to route temp and cache folders from moodledata to SSD drives (due to latency).