I am aware that it's most likely related to DPI not being set right on fastboot. Setting scale to 175 then 200 will fix it yes. Automating it sounds nice. This workaround has been known since page 1 of this thread.
What I'm trying to do is determine whether SensorService is causing all this in the first place, so that when this problem gets acknowledged, said service could be looked into as a starting point(all the people I see having this problem is using 2-in-1 style device). It's not restarting of this service that fixes it, disabling it does - for me at least.