I somewhat agree on #1. I've got an Adventurer at the moment that I spent quite a while totting up what I was actually wearing, on visiting a shop, so that I would not sell what I wished to keep even while trading spare items. Add to that some better way of displaying the left-hand list (perhaps a search similar to Dwarf Mode's trade-goods assignment), because trawling through for the best quality hoods (and cross-comparing with what I already was wearing) was more tedious than I would have liked.
For #2, you may not be aware of the "Job Manager" function. You can assign multiples of items (up to 30 at a time, but with no practical limit on how many times you request 30 items). The main disadvantage with this method is that you can't ensure that a given workshop (say the mason's one linked to the marble stockpile) is the one that gets given the jobs, so your 14 marble tables may not be made (or may be made of marble in a workshop which is not restricted to Skilled or above masons). Also, you need an assigned manager to "file" the jobs.
I don't know if the lack of workshop-assignable multiples is deliberate or not, but I tend to think of it as a 'reward' for assigning a Manager (and ensuring he has time to work on managing things) that such multiplicities can be defined. (Although for fine-control of jobs, I still prefer to manually assign to workshops.)
For some industries, I'd also suggest you set up an array of workshops. You can perhaps then assign 3 (single) table job requests and 3 (likewise single) throne requests to two workshops in four and 4 tables and 2 thrones to the other pair. I find that I'm always wanting to produce something en-mass insofar as masonic works go (even if its just blocks). Unless I'm lucky enough to have two or more Legendary armoursmiths I would resort to micromanaging a mass-requirement of armour pieces, actually. (Yes, however, it would be nice to ask for a couple of dozen helms specifically in the workshop to which the skilled armoursmith concerned is given sole working rights.)
For #3, there are settings (somewhere in the INIT files, but I can't recall exactly where right now) that might be what you're looking for. The default "Pause and zero in on 'hit damp rock' events", etc, can be made to not pause (or pause but not zoom to the locale), if that's annoying to you. However I may be misreading this request because your excellent vocabulary (with mildly fractured grammar in its formal style) is a bit too tersely expressed on this item. Please feel free to expand on any point that I'm misunderstanding.