Some ROMs have the boot.img fstab files mount just /data as F2FS (like a Moto X). Others mount all partitions as F2FS (haven't found any threads comparing benefits of doing all vs. just /data)
/META-INF/Com/Google/android/updater-script needs to be modified to format and mount the appopriate partitions as F2FS.
So for a phased approach, say getting toes wet with just setting up /data for F2FS, is it just
1) editing the ThunderKat_manta-KTU84M-20140607.zip boot.img fstab and changing
/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic, data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic, data=ordered 0 0
format("f2fs", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/userdata", "0", "/data");
Am I on the right track? Miles off?
If I'm on the right track, what's required to do all partitions as F2FS? Would I have to put the ROM to be installed on a USB stick via USB OTG so that the recovery could find it after all the formatting?