That's because drivers do not look for API "patterns of inefficiencies". The optimizations are either in global settings like resource distribution (found throu

That's because drivers do not look for API "patterns of inefficiencies". The optimizations are either in global settings like resource distribution (found through extensive profiling so impossible to do automatically in the driver) or optimized shaders (again, guided by profiling and not even possible at the app level since the game cannot ship with the native shader code). If you ever wrote C/C++ code with the performance requirements you know that different programs will run fastest with different compiler options, drivers provide these optimal options for the different games and if you change the name of the game the options are likely to become non-optimal.