I'm quoting your post from the other thread as this relevant to this discussion.
Oh dear...
The first thing we have to establish is that are several varieties of CTRTransfer. While it's true that those like [3ds.hacks.guide]
Standard CTRTransfer and [3ds.eiphax.tech]
Manual Transfer {when used as instructed} does not copy console unique files outside of their intended or original 2DS/3DS system from where they were sourced, the CTRTransfer Tool you were referring in
post #11 is not one of them.
This form of CTRTransfer does erase the target system's unique files by supplementing or replacing them with those from a target system. In fact, reflashing the entire CTRNAND with a donor's ctrnand *.bin image is actually one of the key aspects to
Lazarus3DS (aka, last ditch nuclear option meant to repair worst case firmware softbrick where the NAND is fully trashed and no SysNAND *.bin image backup exists).
***
While your idea of selectively restoring the
movable.sed and nand
*.dbs does work in terms of being able to play another/source system's library (
Nintendo 3DS folder), the
movable.sed contains console unique information such as a copy of the
LocalFriendCodeSeed_B (responsible for online play access), access rights to the
Nintendo eShop (eShop account) and who's NNID + DeviceID that
movable.sed is supposed to be registered per their CDN server records. The same goes for your private legit eShop tickets found in
ticket.db. Those have signatures specifically to the device that bought the titles.
It'll be pretty stupid to broadcast your presence, such as your Friend Code, from two places at once. Taking that target system to play or shop online with the cloned setup is asking for Nintendo to ban both. Extra negative points if you give a reason for Nintendo to suspect stolen identity or fraud (ie, credit card info linked to eShop) and to hyperban them both.
***
Also, it's not a good idea to transfer only the nand's
title.db &
import.db to a different system as these two database are intricate to what's installed or listed in the
title folder. You can softbrick the 3DS firmware due to differences in firmware versions and ContentIDs names for the APP files.