Hi
If I setup two rectangles I can achieve some distortions on the (auto) generated UV’s if I modify the mesh acting as the texture mesh. But I’m unable to actually get something useful out of it, like having my texture mesh at different resolution defining an arbitrary warp of the projection.
I come from very old software that used to have “mapping primitives” as one way of texturing. Example here, where a subdiv object is mapped by a “disk mapping” primitive as one of several options, whereas in Blender the only “primitive” is a rectangle/cube (shift T) that can be repositioned and scaled, but not rotated (afaik).
The only reference I could find about texture mesh was devs asking if it should be removed 
Is it planned to improve on the usability of texture mesh and/or other primitives defining a texture space “projecting” perpendicularly from the primitive texture space onto the actual mesh, using “object definitions” like planar (which we already have), spherical, cylindrical, cube, disk, cone (flat cone = disk), and mesh?
So I’m wondering what the intended use is for the feature Object Data/Texture Space/Texture Mesh actually is?