Note that the slew-to-tracking issue only appears when slewing from a situation where the mount is not tracking previously (e.g. parking).
When slewing when already tracking (e.g. one object to the next), the mount does initiate tracking after the slew.
This is inconvenient when e.g. running an automated schedule from park position.

With regards to the connectivity issue I described in my last post: I was not able to reproduce it today.
I tested with 3.5.6 beta and 3.5.2 stable on a Pi3 with 4GB.