PPPoE connections on W8.1 - would a tutorial be worth it?

Compare Internet Options, the Connections tab on Windows 7 and 8, and Windows 8.1 (or on IE 10 and IE 11 respectively). Do you see a difference?

What you see is another functionality being ripped out of Windows for no apparent logical reason - this time it is something so basic that it will stop me from upgrading to IE 11 on my Windows 7 system.
Let's get to the point...
Some of us, not many, but quite a few, have a network setup where our ISP requires us to dial through WiFi (or wire), our router in bridge mode and our ADSL line to a Remote Access server which wil provide a network configuration for our system and enable network connectivity. It is similar to VPN, but not exactly the same.
This has worked from XP to Windows 8. And now it is broken. They told me - BY DESIGN..

What does this result in? I can tell you, significant discomfort. You cannot rely on your system to connect unattended. Moreover, a more obscure unknown flaw results in every initial attempt to connect failing with ''modem'' error 651. You have to dial again.

I do like to try new things, so I upgraded my ''showcase'' Windows 8 installation to Windows 8.1. You can't ''downgrade'' to IE 10 so I set about finding a workaround. I found one. My Windows 8.1 system now automatically connects. And now let me get to the point of this post:
1. Is there a point in turning this workaround into a tutorial?
2. Would someone with more tutorial expertise and time on their hands than me take the lead in writing one?

What are the flaws of the workaround? First, it makes sense only on a stationary system, because it will always be triggered (that's why it is a non-starter on my Win 7 main system which moves around and uses different networks).
Second, if you lose the connection to the RAS server, it won't reconnect. Them in Redmond ripped out redialing options too, and I can't work around that.
The solution involves a double whammy. A batch script in the Startup folder - this will trigger the first dialing attempt, the one that always fails.
Then, a Task Scheduler task triggering the same batch script, for a second attempt which will (generally) work.
So, what do you think? Is it worth the effort?

Tutorial please! I'm getting to the solution, but a tutorial would be nice just in case....

This batch file unfortunately must include one's PPP username and password in plain text. I can't promise I'll be making a tutorial (in fact I'm pleading with someone else to do all the procedural writing), but as you say you are working towards a solution - do you need help with something specific, a stumbling block perhaps?

I Remote Desktopped into my 90 km away W8.1 system today, so it seems that my solution is kinda stable.