Global rules vs local web.config rules - which runs first?

Hello,

in shared hosting environment where Let's Encrypt certs are being used I would like to use rule:

<rule name="ACME" stopProcessing="true"><match url="^\.well-known(.*)" /><action type="None" /></rule>

on global IIS level to not redirect any request for URL's containing well-known part for Let's Encrypt certificate verification. Some users are redirecting to www and some are redirecting to SSL. Let's Encrypt domain verification must access its generated files without any redirection. I've tested mentioned rule in client web.config file at the beginning of rules section and it worked. I've moved this rule to global level and it looks like it is not stopping parsing rules anymore. So now I would like to maybe ask for small clarification.

1. Does global rules run first?
2. Does global rules processing is completely separate from web.config rules processing?
3. Can I stop somehow processing local web.config rules on global level based on URL containing part of well-known?

Thanks

EDIT: On page https://www.iis.net/learn/extensions/url-rewrite-module/using-global-and-distributed-rewrite-rules there is information "Global rule set is always evaluated first, and after that distributed rule set will be evaluated by using a URL string produced by global rule set." but there is no information how stop processing param on global rule is affecting distributed rules processing. For now it looks like stopping processing global rules is not stopping of processing distrubuted rules.