You said:

Here the @Windows Services Blacklist-keyword could be replaced by "^spupdsvc$|^TBS$|^Sysmonlog$"

but that's not truth because you used [Result is FALSE] mode in global regexp.
So this is a "boolean negation" and this is a single way to perform negation in zabbix as Posix ERE (server side) doesn't support negation.

About LLD filtering - you probably don't know about ZBXNEXT-581

You're right about the negation and the only way to perform negation in zabbix without the use of negative lookbehinds and lookaheads forming very complex regexes, not sure if supported by Posix ERE. I completely overlooked the fact that the filter field expects a TRUE to have a value accepted not to have it filtered out. Result is TRUE in my example would make my example valid (but not doing what it was intended for).

I indeed did not know about ZBXNEXT-581, which looks promising to solving my initial problem if it will be possible to adapt a templated LLD Filter on host-level as this is not clear to me by the added documentation for this feature.

Additionally an ability to use some kind of zabbix-specific regexps syntax allowing one to simulate the current global expressions behaviour in a local regexps could also be very handy for use in trigger expressions.
For example: !

to get this boolean negation only available in global regexps
so !{^spupdsvc$}|!{^TBS$}|!{^Sysmonlog$} would represent
1 » ^spupdsvc$ [Result is FALSE]
2 » ^TBS$ [Result is FALSE]
3 » ^Sysmonlog$ [Result is FALSE]

or !{^spupdsvc$}|{^TBS$}
1 » ^spupdsvc$ [Result is FALSE]
2 » ^TBS$ [Result is TRUE]

This, in combination with the ability to combine global regexps with local ones would correct my previous erroneous example like this:
Filter macro:

regexp: @Windows Services Blacklist|!{^service1$}|!{^service2$}

Then of course also usable in item or trigger expressions where ZBXNEXT-581 won't be of any help..

Thanks for the nice discussion! Your idea is interesting and probably is fresh.
Take into account please ZBX-3924

Using PCRE, as suggested engine in ZBX-3924 for regexps both on front-end en back-end, would make it possible to negate using negative lookahead:
My previous global regexp:
1 » ^spupdsvc$ [Result is FALSE]
2 » ^TBS$ [Result is FALSE]
3 » ^Sysmonlog$ [Result is FALSE]
could be noted in PCRE as
^(?!(?:spupdsvc)$).*$|^(?!(?:TBS)$).*$|^(?!(?:Sysmonlog)$).*$
or
^(?!(?:spupdsvc|TBS|Sysmonlog)$).*$
(I think.. I'm not really a regex-wiz )

Not really easy to read or construct (in my opinion), but possible, so using PCRE on both front-end and back-end as suggested in ZBX-3924 would make a zabbix-specific syntax for boolean negation unneeded.

So going back to my example combined regexp
@Windows Services Blacklist|^(?!(?:service1|service2)$).*$
could internally be converted to this PCRE regex:
^(?!(?:spupdsvc)$).*$|^(?!(?:TBS)$).*$|^(?!(?:Sysmonlog)$).*$|^(?!(?:service1|service2)$).*$