I did plan to release some files to support f2fs at one point, but didn't end up doing it due to a couple of challenges:
1) kernel support. This requires compiling a new kernel with the f2fs code added, or building a external kernel module to be loaded at boot time. The thing about kernel module is that it needs to match the existing kernel exactly. I can support the F6 stock kernel (MS50012b) based on LG's released source. I am not sure about kernels for custom roms though. If you're using the stock kernel (the exact version), I can supply a kernel module. Actually, it'd be a good idea for me to update the f2fs code since there have been many updates since I first built one.
2) lack of f2fs utilities. A way to create a new file system is necessary before files can be copied to it. Newer Android and newer TWRP versions both support f2fs. Unfortunately, the F6 has neither. Actually, I think hroark13's TWRP v2.8 is supposed to include f2fs support, but the kernel used in that port does not support f2fs. If a user has another way to create the file system, it's possible to do so and copy files (by restoring a backup directly to the SD) outside of the F6. Unfortunately (again), when I looked into it last time, there was no easy way to do this on a Windows PC. So if you can use Linux or use another device (with a TWRP version that supports f2fs) to do this step, I can give instructions to see whether that would work. Otherwise, I would need to come up with a more convenient and user-friendly way to deal with this issue.
I think it's a good idea to transition to f2fs, or at least use fstrim regularly on ext4 file systems. In the past, people use f2fs or fstrim for performance reasons, but with today's cheap flash memory (both in price and in quality), I think it makes even more sense to do it for the sake of longevity. Anyway, let me spend some time to investigate these two challenges again.