Rasters.jl wraps NCDatasets, so you will never be able to import a Raster into it, as it would be a circular dependency.
The end goal of Rasters.jl is that you will do the majority of most raster workflows you would do in NCDatasets, ArchGDAL and other backends like GRIBB etc just in Rasters.jl, and it will take less code and be essentially the same for all backends. Mostly that is already the case. As far as I can tell everything you are doing is contained in these lines:
# Load your variable as a Raster and divide it by 100
newvar = Raster("original.nc"; name=:orgvar) ./ 100
# Change the name:
newvar = rebuild(newvar; name=:newvar)
# Update the units in the metadata dict
metadata(newvar)["units"] = "meters"
# Create a new netcdf file
write("new.nc", newvar)
Although I cant test it. It’s always better to link to a downloadable file we can all use so your code is a MWE (minimum working example).,
Edit: notice that attributes are called metadata and where you specify the variable we specify name. This is because none of this is NCDatasets.jl specific. Its just generic DimensionalData.jl syntax, which applies to all backends in Rastesrs.jl, and to other non spatial packages as well.
We also use Symbol for variable/raster names rather than strings.