Honestly, just use VTF crosshairs. They are always perfectly centered, can never get off centered, you can adjust the size and color from ingame easily, you can use different ones for different weapons and they are much easier to transfer over to a different HUD when you want to change your HUD.
Here's the link to the VTF guide:
http://www.teamfortress.tv/35367/vtf-crosshair-pack

And here's a link to a bunch of alternative crosshair files:
https://dl.dropboxusercontent.com/u/49819530/crosshairvtf.rar
"ql_7" looks pretty much like the one you're using.
If you don't like the outlines let me know. I should be able to remove them for you.

I don't really understand what you mean?
You mean when the scout shoots you just when you start the jump and duck at the same time?
Like what happens when you use a crouch-jump script and get juggled more when rockets hit you just as you start jumping because it's basically like a rocket jump with someone elses rocket?
If that's what you mean, then doesn't the same thing happen with regular rocket jumps?
Also, you only crouch when you let go of mouse1, so slightly after your jump, so I don't think it makes a difference.

About the whole scripts make it impossible to learn rocket jumping thing:
Ok, maybe there are a few jumps where scripts can hurt you. The thing is just that I'm using my scripts for a while now and have yet to come across a jump where I felt like my scripts don't work for this situation.
That being said, I don't play jump maps and I don't claim to be some kind of expert jumper. I just use jumps for rollouts on regular maps and getting around the map.
If you're doing some crazy complicated jumps on jump maps I guess scripts can be a problem sometimes, but as far as just normal soldier gameplay goes I don't really see it.

Also, I still have jump and crouch bound to keys without any scripts, so if I for example want to do a jump without crouch (to get on top of a small ledge without taking fall damage or something, like the health packs on process mid) I can still do that.

Without wait commands it's not possible to make a script that lets you just to c-tap jump with a single button and makes it completely fail save, but I made a script that makes it A LOT easier:

bind "mouse2" "+ct"
alias "+ct" "+duck; bind mouse1 +ct2"
alias "-ct" "-duck; bind mouse1 +attack; -jump; -attack"
alias "+ct2" "-duck; +attack; +jump"
alias "-ct2" "+duck; -attack; -jump; bind mouse1 +ct3"
alias "+ct3" "+duck; +jump; +attack"
alias "-ct3" "-jump; -attack"

It's basically the same as above, I just have a 3rd alias to make it so that you'll crouch right after the jump and you can keep pressing your c-tap key (mouse2 in this case) to stay crouched in the air and chain further jumps (pogos, walljumps) after the c-tap real easily by just pressing mouse1 again.

Like I said, this script makes c-taps a lot easier. The timing with regular c-taps needs to be close to perfect and is really hard to master to a point where even with practice you'll mess it up sometimes.
But with this script the timing is super forgiving. Even if you mess up the timing a little you'll still get a higher than regular jump instead of a super weak jump like when you mess up a normal c-tap.
Took me like 2 or 3 tries after making this script to do a perfect c-tap and never messed it up since and using c-tap jumps all the time.

Edit: mouse2 still functions as a regular crouch button outside of c-taps btw, so you don't need a extra key for this.

Also, I'm not sure if I agree with all this "you'll never learn to rocket jump properly if you use scripts" talk.
I use scripts for regular rocket jumps as well as c-taps and I'm pretty sure there's not a single kind of jump that can't be done with those scripts and binds I'm using. Rocket jumping is mostly about where you're aiming, the timing of when you shoot a rocket and what you do with your WASD keys. Those are the things that need practice. Scripts don't do any of those things for you. They only change if you have to press 1, 2 or 3 keys at the same time.
It's not like it's hard to just press 3 keys at the same time and you need to practice and keep practicing it to be good at it. I can rocket jump with 3 keys just fine, it's just more convenient to just use 1 instead...
And yes, I never learned to do regular c-taps, because I'm using a script for it.
But the thing is: I don't have to. I can c-tap just as good as the next guy (probably more consistent than most) with my script and there's no downside to using it. A c-tap jump is a c-tap jump.

Are you still working on this?

Could you or someone else give me a link to thalash's vtf crosshair please?

People just need to start playing FaceIt.
It has the greatest potential by far, most support, frequent updates etc.
It might not be the best yet, but if enough people would use it it could easily become far better than the current options.
It's kinda sad that FaceIt is such a huge chance for comp TF2 but the community has to act like whiny children and ruin it.
Obviously there's gonna be some problems in the beginning and obviously it's gonna take a bit to find matches if everyone says "there's not enough players there, not gonna use it".

Yeah, it's most likely your HUD.
https://www.reddit.com/r/tf2/comments/57760o/cause_and_fix_for_serious_fpsdrop_issue_involving/?st=iu7rmtqe&sh=79464249

Could you post the source of that gamebanana mod?

Could someone make a Circledot crosshair (the one from OP), but without outlines on the outer circle?
And maybe more clear/visible outlines on the inner dot?

Also: If you just want to use the same crosshair for all weapons and only use VTF over HUD crosshairs, because they are easier to use, but don't feel like manually changing the files for all weapons to the same crosshair, you can use this console command:

cl_crosshair_file ../replay/thumbnails/crosshairname

you don't have to replace ".." with the exact directory, just leave the dots there and replace "crosshairname" with the name of the crosshair you want to use.
Also a great way to test all the crosshairs without having to always close the game, change the file, restart the game every time.

There's a lot more to a good mouse than that.
A mouse that pits your hand perfectly but has a shit sensor it will still be a shit mouse.

Any yes, a good sensor is definitely important.
You don't need the best and newest sensor and you definitely don't need a gazillion DPI, but if your sensor has build in acceleration, is super inaccurate, jittery etc. than that'll hinder your performance a lot.

My personal recommendations:
Zowie FK1/FK2/FK1+ (1 is larger than 2, 1+ is even larger), Zowie EC1-A/EC2-A (again, 1 is larger than 2) and my new favorite: Logitech G Pro.

One of them should have a good size/shape for your hand and all of them have absolutely flawless sensors and are very well build and have no unnecessary marketing gimmicks like 100 buttons or 8000 DPI and are designed with FPS gaming in mind.

Normally you shouldn't have to do that.

Just go to your GPU settings and choose stretched/full screen under scaling options and check that ignore scalin settings made by games or apps box.

Dito.
And if I choose min-mode the installer crashes every time :(

Give me one example of an appropriate answers I wasn't willing to receive.

Without arguing you can never get a real answer. If you don't argue anyone can just say anything he comes up with on the spot and you'd have to accept it as fact.

I think it's childish when people can't have an argument without feeling it's a fight or competition of feeling the need to turn it into one or when they think arguing is a bad thing and shouldn't be done.

I never said that either is bad.
I only said that if the argument is that 75 FoV is bad "because you see less in your peripheral vision" then the same can be said about 4:3.

What I'm actually saying is that, if you wanna call anything "bad" to begin with, then 4:3 is worse than 75 FoV.

I agree with most of what you said. It's definitely personal preference and while with some stuff you can argue that one has objectively some advantages over the other, using what you're comfortable with/used to is definitely more important.

Just to adress your m_yaw 0.0165 thing: it doesn't solve the problem. It just turns a visual disparity between X- and Y-axis into a 'numeric' one. With m_yaw 0.022 the senses are the same, they just look/feel different.
With m_yaw 0.0165 the senses are actually different, but they look/feel the same.
It's personal preference again, but it by no means nullifies the problem.

Uhm I'm not.