Yeah, trunk-based development, in my experience, is almost always working on trunk and using FFlags to eliminate integration, especially for smaller changes.
Bigger changes can work on trunk but require as a lot of care (aka energy) and so I do sometimes see bigger feature branches, but then you have to make sure to merge trunk into that branch very often, which has a whole other host of difficulties.
In my experience, people then continue to just work the same way (pain in integration) but with the additional overhead of FF.
So, uh, you kinda need to pick one, I think? FF is also a lot easier when you have a more service-oriented/modular approach because then someone working on some service somewhere can do a big refactor without impacting someone else...