Please also read:
Extended Comparison: Transparent RAID vs. RAID over File System

RAID-F vs tRAID

FeatureRAID-FtRAID
Snapshot RAIDYesNo
Real-Time RAIDYes, but experimentalYes
Live data reconstruction in the case of a drive failure?No. The failed drive must be recovered.Yes
Various RAID engines and Multi-Parity supportYesYes
Are surviving drives fully readable/writable even in the event of failure past the tolerance level?YesYes
Supports drives with existing data on them?YesYes
Can a drive be pulled from the RAID and read in another system standalone?YesYes
Supports any file systemYesYes
OS support?Windows and LinuxWindows and Linux
Datarot detectionYesNo
Can RAID include specific folders, specific data set, media drives, and ad-hoc content?YesNo
Ability to exclude certain content from the RAID?YesNo
Recovery of specific filesYesNo, only recover a whole drive. Has no concept of files.
Supports network mapped drives as part of the RAID?YesNo
Can upgrade from a small drive to a bigger drive by just copying the data over and without affecting parity?YesNo
Vulnerable to the Snapshot RAID sync hole?- Yes if Snapshot RAID (see Understanding the limitations of Snapshot RAID)
- No, if Real-Time RAID
No

Summary

As you can see, tRAID is not a replacement for RAID-F.
RAID-F makes some pretty compelling arguments.
Where tRAID wins over RAID-F is in that its real-time RAID feature is far more robust.
As stated above, please also read the detailed text comparison of Transparent RAID vs. RAID over File System.