On a sang/ramps/arduino/rumba - Colour TFT chews up heaps of memory and involves ugly pre-loading of image pages. Yes its 'just a library' in Arduino land, but a slow painful library that will break the approximated realtime control. You also don't have enough free memory for all teh variables - even on a 2560 (so double a 1284), you end up with 2/10ths of f-all left - and thats just with a DOGM display....
Note the 'seems similar to the link you posted' is actually just a 1-bit display.. not color.
And using one of the TFT displays, having worked with them in many other bit here and there, I can offer only that its a lot more painful than one would imagine, and realistically, I'll file right there in the 'far too much effort, with far too much impact to the firmware (timing, size, free memory) with way way too little benefit'. The touch screen relies on Interrupts - its poll based meaning the AVR must be ready the moment you press the screen and it does this via interrupts - This means that likewise *any* timing calculations in marlin will be well and truly out the window. Just my $0.02 anyway having spent a lot of time with displays on AVRs....
On the RPi, since its not the controller, sure, put whatever you want on....