Seperated Atmosphere folders per sys/emuMMC instances

Feature Request

What feature are you suggesting?

Overview:

• To add seperated atmosphere folders for each sysMMC & emuMMC instances (that can contain different LayeredFS / kip / exefs / nxthemes patches / saves redirection / or even an entirely different version of Atmosphere ) so as not to interfere with other eMMC instances.

Note: This is mentioned in Atmosphere 0.9.0's changelog (Quote: "In addition, some niceties (e.g. having a separate Atmosphere folder per emummc instance) still need some thought put in before they can be implemented in a way that makes everyone happy."), but other than this, there is no other information to be found.

Smaller Details:

• For sysMMC, it can either continue (or by default) to grab /sd_root/atmosphere/ folder for use, or add an extra config line to change the location of it.
• As for emuMMC, the location of the atmosphere folder may be configured in /sd_root/emuMMC/emummc.ini (e.g. atmosphere_path=emuMMC/RAW1/atmosphere) (hekate can also add support to change this line to achieve a fully configured environment without manually modifying emummc.ini)

Nature of Request:

• Addition

What component do you feel this would best fit within?

• Fusée
  
  • Atmosphère's custom bootloader.
    
• Thermosphère
  
  • Atmosphère's emuNAND implementation.
    

*I'm not sure where to fit this in, since I'm not familiar with how the internals of Atmosphere work.

Why would this feature be useful?

This can allow users and developers to quickly reboot to different instances of eMMC to test and use their desired controlled environment, instead of manually altering folders on SD card or even swapping to another card each time they want to use different patches.

*Words and solution are abruptly thrown together, my brain is not really functioning right atm, I can explain more details if anything is unclear.