I've also posted about this before. The only way I could eventually definitely stop Runtime Broker 'taking over' was to end the process each time the computer was turned on but this was a pain to do each time. But I just got into the habit of doing it.
But since a week or two ago, after a very significant update of Windows 10, the problem really does seem to have finally been sorted. I haven't knowingly changed anything but Runtime broker now never uses any significant amount of RAM or processing power. I thought I should post this in case you want to try again with Windows 10!