Hold it. Please watch the video i have made where i create the footprint : watch how that lattice structure is created in the paste mask.
This is needed for assembly of the board.
The assembly house that will solder the components will ask the PCB designer to give them the mask layer. (Layer means : a single Gerber file) Even if the program internally treats these things as object, at a certain point they are all collected and sent to a single Gerber file. That is why we call those a layer. They may not sit in a 'layer' inside the program , they are a layer of the Gerber stack.
We don't know how the program internally works. All we can say is : at the end of the day we need a single Gerber file with the information of all the openings we need to create the paste mask. In 'Gerber' speak : each file defines 1 layer in the Gerber stack. Irrespective of how the cad program does it internally. It may very well be that the paste definition is simply a parameter attached to the pads and , as such, does not exist as a drawing layer in the computer. When output is generated the parameters are collected and sent to the Gerber processor. Fine. The 'layer' is created at that point.
So when PCB designers talk about layers they talk about GERBER layers.
The reason they call em layers is because they were fotoplotted on film. Put the films on top of each other to get the board. 1 film = 1 layer in the stack.
The assembly house will NOT alter the mask. If they experience problems during manufacturing they will call you and tell you : you need to decrease the paste x amount smaller or larger than the pad for this component , you need a lattice here of such and such.
At that point the OCB designer needs the capability of a manual override.
Having an automatically generated paste mask is good, but you need to retain the capability to override. Override is not a 'global' setting. It needs to be per pad. Each pad needs to be able to be manipulated individually and this information needs to be set in the library. You set it up correctly , once , in the library and then you can forget about it.
So : we need individual access to the paste defintion per pad, and the ability insert 'paste objects'.
I suspect DEX already has both. (from what Iliya showed me off-site)
The same goes for airwires. (ratsnest)
Layout happens in stages.
You place a few parts, wire some stuff locally and you create an escape path. Meaning you draw the wires leaving the drawn cluster. These wires stop midpoint. They will be completed at a later point in time. You need to place them so the area required is reserved.
The airwire needs to be shown from the end of the placed tract to where it finally needs to go. This gives visual feedback to the layouter so he can make an estimate of routing density and spatial placement. PCB designers have been screaming for airwire (especially airwires that auto-adjust to always show the shortest pathway) and density maps for years when the first layout programs became available.
Don't take them away.
You are thinking 'old skool' where you would have the pad on the rubylith: take your roll of black tape and make a connection end-to-end. That is indeed how it was done. As soon as airwires were introduced that technique was the first one to end up in the trash can. Too often you had to strip the tape and retry mid-design. Airwires avoid that problem as they give you a visual que of the density.