Moving /storage/sdcard0 from NAND to a removable MicroSD card: will it break anything? Background information

I own a Samsung Galaxy S Relay 4G running Android 4.1.2.  It comes with 8 GB of built-in NAND flash, which is almost full by now.  Luckily, it also has a MicroSD card slot.

My carrier doesn't offer handset subsidies.  I hope not to have to upgrade to a new phone before the BlackBerry Priv comes out:  I want a device with a physical keyboard.

On my device, /storage/sdcard0 occupies 2 GB out of the 8 GB.

Of the 2 GB:


OsmAnd offline maps take up 800 MB.
Downloaded podcasts and whatnot take up about 600 MB.
Google Translate's offline data takes up 200 MB.
The rest is miscellaneous.


Because I'm not running Android 6.0 "Marshmallow" or higher, my device doesn't include support for adoptable storage.

My questions

I'd like to move /storage/sdcard0 from built-in NAND (8 GB) to the removable MicroSD card I've bought (32 GB).  The entire MicroSD card is formatted as FAT32.  In the place of the old /storage/sdcard0, I plan to leave a symbolic link.

I've experimented a bit, and it's clear that I'll have to root my phone first.  That's fine.

I wonder:


Does /storage/sdcard0 include any file ownership or permission data which I don't want to lose?
Will Android (and all my apps) work fine even if /storage/sdcard0 is actually a symbolic link instead of a folder?  If you believe they'll work fine, then how do you know this?  :)
Is there anything else I should know before doing this?
Multiple things in this context:


apps might directly support using the external SD card as storage, check with their settings. This will save you some headaches, as it then works without "tricks". When changing to the new storage, apps might even offer to copy/move their data over, which would be the easiest thing for you to do.
As Gokul mentioned in his comments on your question: it's not as simple as just creating a symlink from the old storage to the new – after the next boot, that is most likely gone (which can be worked around by editing the boot image – or by facilitating init.d with a fitting script, if supported). You could however symlink each directory separately (e.g. /storage/sdcard0/foobar -&gt; /storage/external_sd/foobar, which should do even without root and, more importantly, survive a reboot without "additional tricks"
both external storages use VFAT, so no user permissions covered (VFAT doesn't support them), so "nothing to lose" in this context ;)