@Riot Two Serious Coding Questions

Disclaimer - My internet is pretty good (~30-40mbps) and I live near the new server (40ping), so you can rule out lag for this conversation.

2nd Disclaimer - I know nothing of coding. I'll try to use simple language to get my point across.

1. How hard would it be to make it so that the server acknowledges your champion's geographical location at every point in time during a dash?

Pretty sure mid-dash, I'm coded to still be standing where I was when I started. So in the server's eyes, I stand still for (dash length), then instantly appear at end-of-dash-location.

The game would be immensely smoother, more realistic, and more skill-based if the server had a quicker refresh rate (or something, plz don't hurt me) so that I was acknowledged at every point during my dash. This way you could time a snare/root to make plays, and it might help tame mobility creep. It would also cure the 'randomly walk forward when I A-click a champion mid-dash' thing (I think?).

2. Are you guys considering a complete overhaul on hitboxes at any point in the future?

Hitboxes (specifically skillshots) can behave strangely. Often, they're smooth and feel good. But when that's not the case, it sure is frustrating. We all know the common ones like LB's chain, Thresh's hook, Nid spear, Morgana bind, etc. But it happens with other champs from time to time, such as Gnar boomerang and even the occasional Cait Q.

I ask for two reasons.

A) Skillshots don't seem to align perfectly with their range indicators when playing the champ. It seems to me like most skillshots have more range than their indicators. Some skillshots also feel more wide or narrow than their indicators.

B) Visually, when I'm on the receiving end, often times I feel like I should have dodged skillshot X. Simply put, the visuals don't add up to the server response too often in my experiences.

Thank you for any response. Upvote if you'd also like to have a conversation with Riot about this topic.