nuclei v2.9.15 and use of custom template directory introduce issue

[l0pens]

Hi,
I would like to use a custom nuclei template directory, and play with criteria to select a set of templates.

(A) update templates

instead of doing default (this uses ~/nuclei-templates)

nuclei -ut -v

I do this:

nuclei -ut -ud /data/nuclei-templates -v

so nuclei config includes custom directory in ~/.config/nuclei/.templates-config.json-> "nuclei-templates-directory"
This method is a bit slow compared to the first default one but works.

(B) list templates with some criteria

Then (B) I would like to display list of template that match some criteria using -tl option,

for example list only critical

nuclei -duc -tl -severity critical

I do remark that when I'm using a custom directory, the template list is sooo long, and could includes some warns and sometime hang

On another side, when I'm keeping default template location I've no issue at all to list templates.

Example of warn (when using custom template directory)

   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v2.9.15

[WRN] Could not load template /data/nuclei-templates/http/default-logins/oracle/peoplesoft-default-login.yaml: the template was excluded
[WRN] Could not load template /data/nuclei-templates/http/cves/2019/CVE-2019-17382.yaml: the template was excluded
[WRN] Could not load template /data/nuclei-templates/http/exposures/backups/php-backup-files.yaml: the template was excluded
[WRN] Could not load template /data/nuclei-templates/code/cves/2023/CVE-2023-4911.yaml: yaml: unmarshal errors:
  line 25: field code not found in type templates.Alias
[WRN] Headless flag is required for headless template /data/nuclei-templates/headless/technologies/sap-spartacus.yaml

NB: /data is a volume mount point of docker container
NB2: I created a pull request in order to precise that -tl option could help to search by criteria and verify results without doing some action on target host. cf. #4328

Am I alone to have this (perf) issue ? is that a bug? any hint to fix that ?

thanks

[l0pens]

same in v3.0.3
but I got it ; was due to my container-host anti-virus activity.