Yes, you could materialize the Transpose, that’s probably the easiest solution. Depending on what you want to do with y, you can also e.g. write a custom kernel that indexes the Transpose on the device: Transpose objects are supported on the GPU, it’s just this specific getindex call that isn’t implemented. You could of course also look into implementing or extending the relevant getindex method to Transpose objects.
I’m surprised there aren’t already getindex(::Transpose... methods that forward the reversed sequence of indices of whatever type to the parent array and re-transpose the result, must be some reason that wouldn’t work?