But leaving it on default does not harm: The swapping will only happen once and might (or not) read back the information later on. There is no big or permanent read/write to the swap file - unless you run something really, really heavy or strange on your router!
That's not necessarily true. But (as you implied) the actual activity will vary from user to user and also from one moment in time to another. In other words, it's impossible to generalise because every situation is different and changes over time.
Consider this theoretical example:
Your router is running various services which have a combined memory requirement greater than your RAM (which is why you've created a swap file in the first place).
Your bit torrent program starts up and requires RAM but there is none free, so some of the memory allocated to the DLNA server is moved to the swap file. This is takes time so the bit torrent program is slow to load.
After a few minutes, the DLNA client wakes up to do it's periodic media scan (or because it's been polled by a client device). The memory moved to swap has to be moved back to RAM, so part of the Samba code/buffers is moved into swap instead. Again this is a slow process.
Next, a user tries to copy a file to the Samba share....
Well you can see where this is going
If you are over-allocating memory usage it is quite possible that you will experience significant degradation in responsiveness and load times. But, in it's defence, Linux usually does a good job of working out the best things to move to swap and what to leave in RAM.
Swap is great if you've got a very fast swap device, or you're running a bunch of processes that spend most of their life quiesced such that they don't have to be constantly moved to and from the swap file.
Just my 2 cents.
PS And just to make things more complicated, applications themselves can dynamically alter their memory usage based on available RAM, or even "pin" certain chunks of memory in RAM so that it can't be swapped out.