Remove features deemed 'unnecessary' in upstream Luma3DS
There are some things that you should take note of when using Luma3DS forks:
They may not always be kept up to date with upstream Luma3DS. This is particularly important with the jump between Luma3DS v10.3 and v11.0, where the configuration file format was changed and Luma3DS copies itself to internal memory.
If you experience a bug with one of these forks, you must report it to the developer of that fork. The developers of Luma3DS are not responsible for any issues or bugs that may occur when using a fork unless the issue also occurs with upstream Luma3DS.
Installing a Luma3DS fork
These instructions assume you're using boot9strap (as installed in the guide) as opposed to fastboot3DS, where these instructions may not apply depending on your setup.
Because boot9strap just boots the file boot.firm on the root of your SD card (or on CTRNAND), you can just place any Luma3DS fork onto the root of your SD card as boot.firm. Your 3DS will automatically boot into it as it did upstream Luma3DS.
Download your Luma3DS fork of choice
If necessary, extract it and/or rename the file to boot.firm
Put your SD card into your computer
Copy the Luma3DS fork's boot.firm to the root of the SD card, replacing the existing one
