Hi Simon thanks for quick answer ! We guessed Using different strategies for same scan could be not feasible in ZAP ....
Our client own many https staging site behinds a basic HTTP auth to hide them by search engine, and we cannot control this auth mechanic, moreover we need to test this environment because it cannot be duplicated on our local dev env. This is the only site we can test cause it is surrounded by a big ecosystem of other modules/services
Exploring other ZAP options and plugin we found a solution : using the replacer plugin to force the Authorization header to pass the first auth layer
Thanks for clarifications , have a nice day