This is a different use case - DuckDB is large queries over your entire dataset; Arroyo is continuous queries executing over a live data stream.
So if you have a stream of sensor data from a bunch of IoT devices, you might use Arroyo to run “live” queries over the flowing data, and you might use DuckDB to do analytical queries over archive data
Although they are both hammers to whack nails with I guess, so a lot of use cases likely work well to solve with both systems