ang
<< new primitive always arrive INSIDE >>
Depends what Im doing quite often, Ive already moved existing stuff to one side, and bring in a cube as a reference for an origin centred rotate, say.
Perhaps if I want a new bit of geom somewhere rather than starting with a prim, Ill (find and) loopcut off a (more) suitable bit, dupe it, move it whilst still selected then weld the original back up again.
Variation on above for cylindrical bits find a suitable circular face nearby, extract from it and then extrude and use this (or just extrude (from face) then lop off with LoopCut.
Presumably youre using the Geom Graph in difficult situations as the most recent prim addition is always the last / bottom its easy to select from here?
I suppose a tick box for a user pref to have prims come in highlighted and oven ready might be an idea but thats something to take up with Bj 
Vert | Tighten on multiple selections yep, me not paying attention (slapped wrist job) as with any op on a vert selection, going to work on the total swept volume of the Bounding Box.
Default Commands different from hkeys.
Say you do a full blown vector op MMB rotate, say and choose both an axis and a ref point for that axis to pass thro .
Then immediately after completing the op, press Shift + Cntrl + L or MMB. You can then bind / assign the (vector) rotate op to either the L or M mouse button.
To recall, use Cntrl + L /M and this brings back the vector rotate BUT you can select a different chunk of geom on a different object (if you want) AND select a different axis / ref point all without having to dive into a menu and since you cant (currently) hotkey vector based options, then it’s a way of shortcutting that IS available.
This lets you do the same type of op on different items but using parameters that are specifically geared to that item.
Btw using Cntrl + D (repeat function) offers similar flexibility but will only work on the last op so if you do something different in the meantime youll lose the original / first option.
Putting stuff on a default command will always be available for the whole modelling session (until re-defined) etc.
Since you can have 2 Def Comms (not DefCon, hehe) set to ops youre likely to use on a regular basis then this can be quite useful imo.
All of the above worth looking at but Ill not lose any sleep if you chose to ignore 
Each to their own.
pp
(If I think of anything re ‘multi true-up’ - I’ll post it)