I did manage to confirm that you are correct – reloading the page does cause the new logger (or whatever changes) to be reflected. If you edit something in _web it triggers live reload, but also just refreshing the page (which as you mentioned would spawn a new liveview process for the page) also works.
Is this really the intended behaviour? I swear this has never been an issue before in other liveview apps. Maybe I’m mistaken.
So for the sake of my experiments I’m just heavy-handed adding:
~r"lib/<appname>/.*?/.*"
to my live_reload config, kinda like @kokolegorille suggested originally. I hope this isn’t really the intended way to solve this situation though 
