That was already the case -- the new behaviour being claimed here is that they have disabled previously known methods to intercept the Edge-specific calls. It

That was already the case -- the new behaviour being claimed here is that they have disabled previously known methods to intercept the Edge-specific calls. It should also be noted that almost every element of the windows UI which launches a browser does it using the Edge-specific scheme, so there is a substantial need to do this kind of interception if you are not an Edge user.