No more scheduling + Lazy ToProperty

@meteficha, I've come to your side. Scheduling things implicitly, while makes things easier to program against, also makes things *way* slower, especially in [large applications](https://windows.github.com). It's gotta go. 

This PR also makes ToProperty not immediately subscribe to its source, but only after being asked for the first Value. This means that your constructors can possibly defer initializing properties until they are used. 

This keeps the scheduling around RegisterAsync however, since it's part of the Value Proposition™. 

## TODO:

- [x] Fix up the tests

Closes #435