Which defeats your request, if you can add a "slow' consumer grade device it must deal with caching and swapping in and out. If it has that baggage what is the gain of a 1tb SSD something Vs a smaller one and 1tb HDD out the gate.
Same caching employed , still 1tb storage?
I already explained my reasoning for the default 1TB non-replaceable ultra fast SSD. I'll just copy paste my post in another forum.
With 1 TB of ultra fast SSD, initially, about 8-10 AAA games can be installed on the non-upgradable ultra fast SSD drive while the user still don't have an HDD expansion. But once an HDD is installed all games will be transferred to that storage and the whole ultra fast SSD will be turned into a scratch pad.
100 GB = OS and Apps
250 GB = scratch pad for the actual game being played
650 GB = 20GB of each games are installed
When you start a game, the ultra fast SSD can fill the RAM in maybe 5 seconds, and you'd be playing instantly while the HDD loads the rest of the game to the 250 GB scratch pad.
Up to 30 games (20 GB each) can be installed on the SSD and there will be very quick loading times even on start up or when you change your game.
Additionally, they could enable the latest save of the game with its game assets to be saved on the alloted 20 GB. You could pick your game and in 5 seconds you could be playing your game where you left it off. (I'm thinking 4-5 GB/s to a 20 GB of RAM, so 5 seconds)
If you have more than 30 games, the OS will allow you to tag games that you want as "instant loading".
And then I read the idea of function and I thought that it's a better solution. But we both agree that 1TB as a default is the better solution. It's just that my idea of caching is just too much wear for the SSD. 256 SSD + HDD is a bad idea, IMO.
Use the entire 1TB SSD as a cache for games from either external or optical - longest since used is the first to be ejected - with an option to 'lock' a game in. DD games are locked by default and need to be removed manually, with OS prompts for the user to ok cleanup when appropriate.
Covers all use cases and preferences, minimum user input required, minimises unnecessary writes!
And while you're at it, distribute the games with an emulator/hiberfile type "save state"at the start screen so the game is ready to play after about three seconds. You'll need them anyway for your cloud streaming instances!