To add to Iliyan's answer:
It is not just a matter of having access to the dll files.
Actually if you open this link in your browser "www.yourstore.com/some_category_name#/specFilters=14m!#-!436" you will not be able to get this part "#/specFilters=14m!#-!436" on the server as it is not transferred to the server at all.
The way the Ajax Filters plugin works is also important here.
The Ajax Filters are loaded via Ajax and they are not directly accessible via a URL.
The links that you have are not direct links to a specific controller's action and that is why they can't be accessed via the regular SEO Slugs in nopCommerce.
Let me illustrate this with an example. Let's say you open this link "www.yourstore.com/some_category_name#/specFilters=14m!#-!436".
1. This actually opens the some_category_name in nopCommerce.
2. When the page loads in the browser the javascript of the Ajax Filters sees that there is some hash code #/specFilters=14m!#-!436 and makes a new request via Ajax to simulate the clicking of these specification filters by the client.
So the page loads with all the products in that category and then an ajax called is made to filter them. So it doesn't make sense to make this URLs to be SEO friendly as this pages never get accessed by the search engines.
I hope this makes sense!