Street: Fuzzy match algorithm ignoring directionals

Any suggestions for how to create a matching rule for street addresses that will not match on truly different addresses that only vary by the directional N, S, E or W? e.g., 110 James Dr W Vs. 110 James Dr E   I'm currently using Street: Fuzzy match, and it also matches on East Vs. West, but those really shouldn't match. The resulting problem is that users are blocked from creating the 2nd address and have to request an Admin to temporarily turn off the duplicate rule, which can lead to delayed sales.

I know why it is matching, because the algorithm works based on a weighting of the components of the address, and in this case, with East vs West being the only difference, it must have unfortunately determined that the entire street addresses match 80% or more.

The following is from Salesforce Help:

Matching Methods Used in Matching Rules (https://help.salesforce.com/s/articleView?id=sf.matching_rules_matching_methods.htm&type=5) 

Addresses are broken into sections and compared by those sections. Each section has its own matching method and match score. The section scores are weighted to come up with one score for the field. This process works best with North American data.

• Street Name (Edit Distance, 50% of field’s match score)
• Street Number (exact, 20% of field’s match score)
• Street Suffix (exact, 15% of field’s match score)
• Suite Number (exact, 15% of field’s match score)

For example, these billing streets are being compared: 123 Market Street, Suite 100, and 123 Market Drive, Suite 300. Only the street number and street name match, so the field has a match score of 70. This score isn’t considered a match because it falls below the threshold of 80.

What percentage is the directional weighted? In my opinion, it should have a large weighting. Any ideas for a workaround so that addresses with different directionals don't match?