Thanks for sharing that data, @mohsen_ej. These are not the denoising stats from the command you posted above, which was initially confusing. They may be a useful starting point for exploration, though. First, a clerical note.
Please make an effort to keep your topics specific, detailed, and focused on one question. Failing to do so makes it harder for people to help you, and harder for others to learn from your experience. Based on the post you linked above, a number of other forum mods have already worked with you on selecting cutadapt parameters for this data. I'd recommend you take some time to learn how the tool works (documentation, paper), and if you have a specific question about cutadapt or how to use it, please create a separate topic.
Here, your question appears to be "what rate of sequence recovery is good enough". I'll focus on that.
Sorry if that was unclear. Running DADA2 with different trim and trunc parameters can change the number of reads recovered significantly. Learn how DADA2 works, choose good parameters, and you can maximize the amount of data recovered from a given sequencing run.
This post is focused on "how many reads is enough". If you're still having trouble understanding how to set DADA2 parameters, maybe we can discuss what search terms you've used, what topics you've read, and what you didn't understand about them. I and many others have written about this topic extensively, and I'd be happy to help you learn to find the information you need more effectively.
I suspect mis-communication here. If you were running DADA2 on the data in the screen capture you shared, trimming left 10nt might be useful. You're not. You're running DADA2 on paired-end-demux-trimmed.qzv, in which the lowest mean q-score on the forward 5' end is 28, and the rest are all above 30, which is generally adequate. You've already removed some nt with cutadapt, so you may need different parameters. Take a moment with that visualization. If you were going to apply trim-left, how many NT would you trim?