Sorry about that. What I found out is that Transmission in a Buffalo NAS can only take a certain number of tracker files loaded before it no longer runs. In this case, there were more than 500, with 20 downloading and around 20 queued. Transmission-daemon would run momentarily before shutting down. I verified this when I ran it followed by ps -A: it would appear in the list of running tasks but after a few seconds would disappear when I ran ps -A again.
To solve the problem, I did the ff.
1. uninstalled Transmission
2. went to the transmission-daemon folder in .config to move the contents of the resume and torrent folders to another place
3. moved the folders containing the seeded and incomplete files
4. deleted the transmission-daemon config folder
5. re-installed Transmission
6. put back the folders containing seeded and incomplete files
7. reloaded only the tracker files in the torrent folder for which files existed in the incomplete folder (because if I loaded all of the tracker files I'd end up with the same problem)
8. did a force re-check of each file in the seeded and incomplete folders so that I didn't have to download each one from scratch
The problem had nothing to do with a defect in the Transmission settings file or the client in my PC, which is why I decided to delete my original post. From what I gathered, Transmission can only have a certain number of tracker files loaded, whether paused, queued, seeded, or downloaded, and this is probably affected by the CPU and memory constraints of the NAS. Given that, I will very likely keep the number of tracker files loaded small and put the rest of the tracker files in another folder for loading in the future.