IMO disk-space issues are a much bigger concern with Nextflow than the potential for a small additional overhead using process substitution. When I was running nf-core/mag on a small cluster, I regularly ran out of disk space as the work directory ballooned.
I think we should in general at nf-core be really careful about spilling to disk and try and keep things small, otherwise these pipelines will not be nearly as generally useable as they might promise with community effort/accessibility etc..
So I'm all for process substitution in general, or to use named pipes!