Other strategies would not only be difficult to implement, they might be counter to the intent of NIST 800-63b. Fortunately, there are multiple blacklisting solutions, so you probably don't need (or want) another strategy.
Here's my reasoning.
First, to summarize from 800-63b, section 5.1, the portion about verifiers (such as passwords) that are directly applicable to checking the quality of the user's password.
By my reading, the intent of 800-63b section 5.1 appears to be:
If this isn't possible via the password-changing interface directly, other strategies would require imposition of those goals via human policy. This would require:
A separate way for users to look up passwords in the blacklist. Since the Windows password-changing interface is dedicated and isolated by design, providing a digital way to do this would be tricky (and printing a book instead would be a usability and maintainability nightmare!)
A way to audit for compliance after the fact (by cracking the passwords using the blacklist as a dictionary). You should be doing this anyway ... but in this case, I believe that it defeats the purpose of the NIST guidance (to ensure that the blacklisted passwords are never used in the first place)
Fortunately, you don't need another strategy, if you only need to do the following:
In other words, alternate strategies are not only not needed -- they would be impractical, provide a difficult user experience ... and may not actually be defensibly conformant.