I would assume so. You just need to be extra careful if you do it to sysnand directly. You have to install the cias of the region you are changing it to, then inject the replacement SecureInfo_A (sometimes B instead for some consoles. Just rename it if this is the case).
Injecting the different region secure info file without installing the correct region cias for it will result in a brick.
I'd recommend doing it on emunand first. Doing it to sysnand directly is probably a bad idea. If emunand boots after you region change it, then it should work on sysnand.
I would on emunand but I don't own a gateway and I tried to inject the secureinfo_a 25 times after i installed the system cias on palantines cfw and it would get stuck at "Writing EmuNAND". then I made a emunand on my other SD and it injected perfectly fine on the first try and this is without palantine cfw.
You'll have to convert the emunand you did get it working on to a cfw compatible one, then install the correct region cias. Check that it boots, then extract and convert back to normal nand image.
CFW EmuNAND doesn't extract from the sd card from emunand tool, I know how to extract it using hex workshop, so i'll do that. But how would I convert it back to the normal nand image?
Dump the SD card using Disk Imager (the tool NAND modders usually use). Then use hex editor to remove part of the first sector and delete the non emunand data. You can look at an existing nand dump you have in your hex editor to see where the nand image starts and ends in your full SD dump. Then you'll have your cfw emunand converted back.
You will need to reformat the SD card and setup emunand again with Gateway menu before you can inject it back for testing as CFW has altered the size of the partition.
It's been awhile since I've done this. Unfortunately I can't tell you exactly where it starts because I no longer have a CFW emunand. I suggest you search the forum/post in an existing thread asking about this as this is as far as I can take you on this. Sorry.
Should be. Assuming it was 4.x fw then it should work on sysnand. NATIVE_FIRM doesn't have to be installed in this case as it's the same title ID for all regions, so I would assume the one you had before will work. Since NATIVE_FIRM wasn't altered, you won't have brick issues. If emunand boots, then it should boot on sysnand assuming you had injected the new region SecureInfo file already.
I've been playing fallout4 all day, I went into a elevator and it kept going, never stopped, waited 5 minutes, must of been a bug. How bout you, whatcha do today?
Injecting the different region secure info file without installing the correct region cias for it will result in a brick.