Hello
@TurdPooCharger , I just now went on attempting the method you suggested, however the results were quite confusing
The result that I got was a target 3DS home menu with few apps (them being FBI and the old Homebrew Launcher) which I had previously installed on an old SD card (making them the only two titles my source and target SD Cards shared) though I'm not sure if it matters, however these 2 apps didn't show a 3D banner and were just present in the home menu as an icon, any other app did not show up, both legit and non legit titles from the source 3DS
Note: I went on booting faketik to try and see if it was just a matter of missing titles, faketik managed to install tickets for every missing app, however none of them showed a 3D Banner and if booted they give out a generic error and force me to reboot (this goes for the two already present apps as well)
Secondary note: the home menu theme I had installed on the source 3ds was successfully ported over
I'm gonna write off the steps I followed in details so you can quickly tell if I messed up/missed something when doing the process:
First off I followed the guide and I backed up my Source 3DS SD folder by copying dbs, extdata and title folders out of SYSNAND SD, first
I copied the contents on the (new) target 3DS SD Card, making sure it had double the space of the content I was going to copy
I then proceeded to create a dummy, empty "Nintendo 3DS" folder without nothing inside it
I booted GM9 on the target 3DS and I noticed it was missing the [A:] SYSNAND SD drive, so I wasn't able to copy the contents there, what I did was boot up the system once to let it create an ID0, making the directory reappear, I shut down the system, botted GM9 again and this time the directory was there (along with an ID0 folder inside the Nintendo 3DS folder) and started copying the 3 folders I backed up from the source system's [A:] drive, after the copy finished I fixed the CMACs with GM9 version 1.9.1 (I've been using this version for the whole duration of this operation, both on the source and target systems), and then proceeded to reset the Secure Value by navigating to SYSNAND CTRNAND>data>id0>sysdata>00010011>00000000
After I did that I reboot my system and the result was the one mentioned above, I'm not sure about the [A:] drive missing part, so I'm guessing I missed something on that regard, if you could analyze the situation and possibly tell me what went wrong I'd gladly appreciate it, thanks in advance!