File exchange is a complex topic in any system. You can of course generate URLs as text, which can be included in a CSV export. But you need to keep in mind that URLs are links; the system that sits behind these links still needs to handle access, ie. authentication. In r3, file access is managed via access tokens, which are part of file access URLs - these are generated whenever you click on a file to view/download it and have an expiration date.
In short, while it is technically possible to generate valid links to include in CSVs, it´s not practical.
Why do you expect that files should be included in text formats like CSVs? Do you use another system that does this?
Besides the options that r3 already offers for mass file export (REST calls, save to disk, send via email attachment), the only other option I can think of would be to generate Zip files on the server for convenient download by users. This could be implemented technically, but you would loose the association between the files and records. For data exchange purposes, storing files as base64 in JSON or XML files is another option, but it´s inefficient and I doubt you had something like this in mind.