1) I think scouting is lots of fun. The people who find it more time consuming, I suspect, are either trying to do it all at once - which is not the way to do it - or having a hard time getting efficiency worked out. For those who want to eliminate level 1, keep in mind your own hosted camp gets you straight to level 2.
2) I have no idea what this means. You can flag recruits, and they show up on recruiting home. That's my target list, color-coded to help keep priorities straight.
3) I have no idea what this means. Are you saying D2 projected players aren't good enough, and you need to wait for second session for D1 "pull-downs"? Fine. Just like before. You still recruit in the first session, as you jockey for position. This goes into how you are prioritizing.
4) New jobs is a problem. EEs are dealt with through adapting your recruiting strategies. It would be realistic and advisable, I think, to code more players to have the late preference, create some "breakout" jucos specifically for the second session as clean slates for everyone, and lengthen 2nd session recruiting by a day with 1-2 signing-free cycles to start.
5) I think people are confusing effort credit and consideration signing odds. If you get to only 35% effort credit in a 2-way battle, you aren't getting past moderate. The threshold is something over 35%, probably around 40-42% I suspect. Then you're high, and your chances for signing are a lot less (probably 10-30%) than your effort credit would indicate. In beta, there was big discussion over eliminating the denomination between high and very high. This was ultimately rejected, because you still have that window of effort credit within the signing threshold, and then you'd have absolutely no idea where you were.
6) I agree some preferences are wonky and could be much more intelligent. It is pretty absurd when half the top 6 players in a world "want rebuild", as in Naismith. The vast majority of top 100 players should want success, want playing time, and want a strong conference, and most of them should be waiting to see how EEs shake out, so they should be coded late. This is my only real critique of 3.0.