Well, if you are trying to replicate the appearance of orthophotos, I'd suggest you start by looking closely at actual orthophotos.
Simple noise generators like you find in typical graphics software aren't remotely up to the task of creating a convincing mountainous elevation map. Also different mountains look different, and they also look different depending on the scale.
If you aren't trying to make a realistic looking orthophoto and are instead aiming for a topographic map, then I'd suggest going for something more abstract with fewer textures. Try looking up "swiss cartography"; the swiss really now how to do maps of mountains. A good convincing elevation map is still really hard to do for this though.
If you aren't trying to produce something that looks anything like a real topography, but is just a symbol that says "there are mountains here" then I'd suggest going much more abstract. What you have is both apparently trying to look like a photo or hillshaded elevation map, but also very fake looking. That combination gives a sense that the map is lying badly. The symbols on a map should not be misleading about how much information they are trying to convey. Similarly, avoid adding textures that are ambiguous about whether they are meaningful or just for decoration.
Most importantly, a map has a purpose. Be very clear about what that purpose is. You need to keep the purpose in mind when you are deciding how to represent things, and even more importantly, what to represent. Just because something is there in real life doesn't mean it needs to be represented in a map. If it doesn't need to be there, adding it just creates clutter that detracts from the important things.
A geophysical map needs to represent mountains in some detail. A political map doesn't need them, and if it has them at all they should be very low key. A detailed road network is important for a road map, but not for marine charts while the chart needs detailed bathymetry information and a road map just marks areas as being water.