You can do the exact same thing with DuckDB as well...

I didn't know that(I don't use DuckDB), but SQLite is very standard and anyone can play with it. Query/UX interfaces exist for almost every imaginable platform even. So I'm still a SQLite recommender for stuff like this.

DuckDB is really for OLAP/Columnar (analytical workloads) whereas SQLite is more for OLTP/Row-based (transactional).

When you start running aggregations/windows over large amounts of data, you'll soon see the difference in performance.

Sure, but the OP is using DuckDB as a way to export some smaller amount of data for someone. That's a great use-case for SQLite, from whatever your real DB is, which for the OP is also DuckDB.