RSK is much more scalable than Eth and most coins but it not the best. I think LN which has infinite scale would be the better option.
Tokens can be built on top of the LN(see RGB and maybe Counterparty? ) and using a system of risk minimized oracles(or trustless?) smart contracts like features can be made with the LN tokens protocols.
Oh sure, it looks like a fine system.
Just not a Bitcoin panacea but a project owned by someone.
Difference between say buying access to LOOM Network servers on Ethereum rather than some integrated scaling solution which remains distributed and permissionless.
"... they are still working on addressing the scalability issues of the platform."
To make the Bitcoin economics actually work, we need to distribute data efficiently. In the long run, a blockchain gets of unmanageable size, if we continue to centralize blockchain projects (read: different projects using the same (side-)chain).
To make this work, we need to decentralize projects. Meaning each project should use it's own side-chain. Blockchain sizes are kept to a minimum, this way we don't need to download data we don't use.
For example, why should I download CryptoKitties data if I don't use/support the project? If they had their own side-chain, the users could download and share the data with other users, while the Ethereum blockchain itself would be of a lesser size.
If Bitcoin itself is able to function with side-chains, why would you want a third party between Bitcoin and your side-chain?
I'm not explicitly against it, but your suggestion is pretty pointless. That third party between Bitcoin and your side-chain will function exactly like a bank or payment processor, which is unnecessary and highly unwanted if you ask me.
I'm not able to visualize what you mean. You mean a LN copy on top of RSK?
LN is a transaction network. What would happen with user-data that the ICO projects gather? For example a social media project on top of RSK. Posting an image would upload the image + format/html data + a transaction to a blockchain (if I'm not mistaken). My guess is that the transaction accounts for the least amount of data here.
RSK chain would still grow to an unmanageable size.. Unless you store the data of that social media project off-chain. Which I see a a possible option too, if done properly ofcourse.