The short answer is yes, but that has nothing to do with Samsung Automation Studio.
Arlo is a cloud integration and does not depend on a hub to work. You would still leave arlo integrated to ST. Then Node-Red with Samsung Automation studio will talk to the ST Cloud via the new Smartthings API. Hub has no part in it . I created a virtual driver that basically keeps track of events passed from Smartthings. Flows in Node red are setup for event based motion triggers from Smartthings and the rest of the stuff polls fairly frequently. Then another flow thay triggers actions in Smartthings when the virtual device is changed in hubitat.
Basically in this setup Smartthings is simply being a cloud aggregator for Hubitat. This concept could be used for any device that Smartthings uses that Hubitat doesn't have support. The fact that Hubitat has a great selection of virtual drivers makes this pretty easy.
The only problem with this design is that if you need to get devices back in Smartthings you are kind of screwed if it isn't a switch. Well atleast once the Groovey IDE is fully phased out.
With all that said you can be hubless now if you just adjust hubconnect to work in a hubless mode as well.
Here is the thread it has beed discussed. If you are interested I will share my flows.
