What's the catch with FRAM?
FRAM is great, however, the technology has destructive reads. Flash technology has a limited write/erase cycles, but the reading cycles are almost unlimited.

In FRAM, each read cycle actually affects the memory and it starts to degrade. 
TI states that they've found the FRAM has "Wear-out free endurance to 5.4 × 10^13 cycles and data retention equivalent of 10 years at 85°C". After some calculations this turns out to be around 2 years of constant read cycles or so (without taking into account ECC).

The reality is that for most low power applications, where duty cycles are low, this is not an issue. You will need to evaluate it for your specific application.

The limit in speed is also present, so waitstates will be added if needed. However, one solution is to load code to RAM, run it from there (avoiding the cycles on the FRAM) and avoiding the speed limit.

There was an E2E post on the topic here that discussed some of the ramifications.

A good App Note from TI about what the advantages of FRAM are as far as security is Here