Earlier quoted context omitted.
Personally I would use htmx and roundtrips for all sorts of modification including data (such as reorganizing two rows in a table). But you'd also do that in an SPA, right? How do you prevent desyncs there? Also for e.g. sorting you'd need a server roundtrip anyway in the (likely) case where you use something like pagination or lazy loading. For sending data, you would just have a reply that instructs HTMX to display…
I mean modifications to the template itself. Design changes, copy changes, etc
What I typically do is render the first bit of data on the server and have the client JS use that as a for changes or new records. That ensures that anything done on the client always matches without you needing to code cosmetics in multiple places but also means your pages load seconds faster than a SPA because the first view is ready to go. When the user saves the entry, you can swap what you generated with the server response a few milliseconds later.