Please describe your feature request:

Earlier default way of execution was template-spray i.e a single template is sprayed across N hosts and this directly conflicted with ratelimit per host implementation as this is prone to race conditions and starts N manager goroutines (where N= number of input targets) which is not good .

With Implementation of scan-strategy in #3075 it is possible to implement rate limit per host for this strategy . In this strategy all templates are executed per target which is ideal for this feature

 -rlh        -ratelimit-host      ratelimit per host (only supported in host-spray scan strategy)

Describe the use case of this feature:

with addition of -rlh nuclei will now have both options i.e

• ratelimit per host
• global ratelimit

as both of them have their different use cases Ref: #292 (comment)

Anything Else

• we can use MultiLimiter from projectdiscovery/ratelimit for implementation where key is hash of domain_name+ip_addr