That ‘seemed’ like it was going to, and should have worked, but it didn’t. I went in the game, moved the two windows where I wanted them, then took a peek at their X,Y positions, and put corresponding commands in the auto_login. It showed it ran the commands, but it didn’t move the windows, but continued to report the windows were at their new locations. I tried unlocking the GUI (for manual positioning) and tried running the commands again (in case that was a thing), and while it said it set them, the windows didn’t move.
So, I manually nudged one of the windows a little, and checked the X value, and now it changed to where it was at that point.
So it’s like manually dragging them around will set the X,Y. The X,Y won’t persist between sessions, and neither /setoption nor /option would seem to ‘physically’ move the two components, even though it reported it had changed the respective values.
Panda 
Update: It’s the ‘/setoption GUIResolution 1.5’ that snaps those two back up as well. It seems like for a split second, it remembers where I had dragged those two elements as I login, but as soon as the UI jumps up to 1.5, that’s when the two are then snapped back to their default positions.