April 3rd, I believe. And it has nothing to do with tower approval.
An aircraft cannot be inside an (approximate) 4 mile final on 13R with an aircraft departing 18L. In the other flow, an aircraft cannot be inside an (approximate) 6 mile final for 31R with an aircraft departing 35L. That makes for 6 MIT (matched speeds) to 13R, and 8 MIT (matched speeds) for 31R. Plus, the way the procedure was written, the tower has to staff an additional local controller (and a local assist) to work the diagonal when it is being used.
The result is a pretty useless runway, when you have 3 other dedicated landing runways to use (18R/17C/17L or 36L/35C/35R). It causes departure delays, not arrival delays if used. The only issue it has caused at DFW is non-stop, endless, frequency blocking, complaining about 17L/35R now being designated a primary landing runway instead of an overflow.
And yes, the change was national, and effects every airport (except Houston, who has the sole waiver) that has CONVERGING runways - as a result of an incident that occurred over a year ago at an airport that has INTERSECTING runways.
I'm curious to see what the next "memo" is going to slurk out of HQ as a result of this latest round of incursions.