Prefix: SAFe in general is an accumulation of buzzwords. Especially geared towards larger organizations. As such I dislike it to on principle.

I will assume that you do accept that Agile overall has sensible elements. Here are some of those that do appear in SAFe. The way SAFe goes about packaging and advertising them: questionable to say the least. As would be customary when we're trying to appeal to a large corporation that wants to feel safe and minimize divergence from processes that can be applied by exchangeable cogs in the machine.

    A release train

Continuously releasing functionality in small increments makes a lot of sense to me and is part of certain Agile principles.

    Kanban and WIP limits

Believe it or not, they mention this. Of course they do, they want to appeal to ops teams. Kanban makes a lot of sense to me. Personally I use it on my teams whenever I'm allowed/able to where we do away with Story Points and just size things about the same into vertical slices. Of course I'm in a constant fight w/ "corporate" about hard deadlines and the "need to estimate" and they don't understand lead and cycle time and how you can estimate using those w/ same-sized tasks sigh

   Refactoring

Yes, they include refactoring as a topic of note. Isn't that awesome? :P It's amazing how much text (and training you can sell I'm sure!) you can write on the simple fact that refactoring may be necessary at some point. XP refactoring mercilessly anyone?