Wildcard Route removal on OpenShift 4.x

From messages exchanged between Andrew/Mark and people from the OpenShift Product Management team it seems that wildcard routes are not supported on OpenShift 4.1 and the date of addition for those is TBD.
It is not clear to me whether wildcardroutes have been deprecated or it is that they have not been implemented yet in 4.X . From the message exchanges received it is not clear to me.

Our current platform (both templates and operator) relies on Wildcard Routes.
We have to evaluate what exactly has to be removed and the consequences of that.

The first obvious consequence is that the apicast wildcard router probably will stop to work because we have a wildcard route to access to it.

We also have to evaluate whether removing the wildcardrouter impacts the functionality of the other elements of the infrastructure and what changes are needed if so, and what functionality impact that will have.
A first important functionality impact of removing the apicast wildcard router is that for every new tenant that the client wants to create, he will have to create a route for it manually, because there will not be an apicast wildcard-router anymore.
And we would have two scenarios: in 3.11 (templates) we would have the wildcardroute and no manual creations of routes would be necessary and in 4.1 we wouldn't have the wildcardrouter and manual creations of routes would be necessary by the client